Sale Code

Tracking Sale Campaigns

I have a table with sale products and codes and pricing

I have everything working with the sale bit but I now want to be able to track orders to see if they order a particular product from a particular campaign.

My original idea was to write a session if they hit this one page; this didn't work.

So, if any item in their order is on the list of this or that Sale, they will get one or another Sale Code.

With all that said, how do most people do this?

This will be a very custom setup and will require you to do some hand coding to get it worked out.

You could make use of the eCart functions to check for a particular item by it's id. If the item is found then you could do some processing like set a session variable to a coupon code. You could then send an email to the user with this coupon code.

I added a recordset that pulls in all the sales. I do a LEFT OUTER JOIN to only pull in those that match.

So, if an item is on the sales list, a Sale Name will show up in the recordset.

When I create the "Column" in WAssist, it works fine until I try to pull the saleName from the recordset. Because most of them don't have a sale, that column result from the recordset is empty or NULL and when I add to cart, it gives me an error:

Microsoft VBScript runtime error '800a005e'

Invalid use of Null: 'cStr'

/standarddetail.asp, line 232

Would the standard "hide if empty" WA function work for this?

I next tried putting the recordset in a form and pulling from that when the add to cart button was pressed. That got rid of the error but now when I try to see the output and bind that new column to the page as text, the text doesn't display...

No errors though.

It's been a while since adding a new column to the cart so I"m a bit rusty.

I'm not sure if I've told you what you need; any ideas what I might be doing wrong?

I think I also need to filter my recordset a little different so that it only pulls in active sale codes.

I'm not sure if the new recordset setup you have is triggering, if it were you should either see the output or get an error. If you can post back with the page that has the recordset in it I can take a look to see if I can spot any issues.

Did you ever try wrapping the 'if recordset not empty' code around the display text when you were getting the error earlier?