Re: Two prices in shoppingcart?
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 12835
interpreted = N
texte = >>[lookup >>db=MusicBeach.db&lookInField=SKU&value=[SKU]&returnField=saleprice] > >This should work fine. It almost exactly matches the example formula >given with WebCatalog, which returns the price field instead of the >saleprice field. Do you have a saleprice defined for every single item >in your database, or is it sometimes blank? If it's blank sometimes, then >this would not work, and the results would be unpredictable. Theory..use a field that is called this_item_is_on_sale. Set the items on sale and via look-up or search that overides the price to the sale price. And when the sale is over you simple clear the fields on the sales items and it reverts back to the real price. We do something like this were we set various products as being the top twenty sellers by a product category and do various searchs and displays based on this and then once every 90 days we tell webcatalog to change the fields back to and then use a template and reload the new top 20 sellers for the prior 90 days by product category. Seems to me somthing with this same theory would work for triggering which items on on sale. And then when the sale is over revert back to the standard price. Just a thought.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
Associated Messages, from the most recent to the oldest:
>>[lookup >>db=MusicBeach.db&lookInField=SKU&value=[SKU]&returnField=saleprice] > >This should work fine. It almost exactly matches the example formula >given with WebCatalog, which returns the price field instead of the >saleprice field. Do you have a saleprice defined for every single item >in your database, or is it sometimes blank? If it's blank sometimes, then >this would not work, and the results would be unpredictable. Theory..use a field that is called this_item_is_on_sale. Set the items on sale and via look-up or search that overides the price to the sale price. And when the sale is over you simple clear the fields on the sales items and it reverts back to the real price. We do something like this were we set various products as being the top twenty sellers by a product category and do various searchs and displays based on this and then once every 90 days we tell webcatalog to change the fields back to and then use a template and reload the new top 20 sellers for the prior 90 days by product category. Seems to me somthing with this same theory would work for triggering which items on on sale. And then when the sale is over revert back to the standard price. Just a thought.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
grichter@panavise.com (Gary Richter)
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
U&P IIS concept (1998)
WebDNA Module with Apache 2.2 (2006)
How do I specify a & character in Grep? (2000)
[CART] (1997)
ReturnRaw context (1997)
[format xs] freeze (1997)
SHOWIF/HIDEIF empty fields (2005)
Quit revisited (1997)
Generating unique SKU from [cart] (1997)
Enterprise Server (1998)
New Command prefs ... (1997)
form data submission gets truncated (1997)
Webcatalog quitting (1997)
Merging databases (1997)
numlineitems possible cache problem. (2000)
Date problems-more (1997)
Summing fields (1997)
[WebDNA] WebDNA vs. php war ;-) (2010)
WCS Newbie question (1997)
security problem (1997)