Re: Passing values

This WebDNA talk-list message is from

1999

It keeps the original formatting. numero = 23674
interpreted = N
texte = >I'm having trouble getting some extea name/value pairs from my shopping cart>to my invoice.>>I have a product that requires custom engraving, so I created three name>value pairs, [persname], [option1], and [option2] that take input from the>shopper on the results template. I can get the values from there into the>shopping cart line item no problem. But no matter what I try I can't get>them to the invoice.Anything that actually gets written to the shopping cart file is already there when the visitor gets to the invoice page. Either the data is NOT getting written to the cart file as you think it is -- perhaps because you're not using Header1 - Header40 field names or TextA - TextE field names, which are the ONLY available fields you can use to add extra data to your cart files, or else that data is in the cart file and you're not using those same field names to view the data ...>I've tried putting &[textB]=[persname] into the [setlineitems] context on>the invoice, then adding [textB] down in the invoice description, but that>doesn't work.That's because you should be using using &textB=[persname]. Remember, put the textB inside brackets when you're using a previously-created textB value for display or in a math calculation, but use the field name without the brackets when you're setting that value in the cart file.>Also, one more newbie question: Is there a way to use an empty field as a>value?Yes!>I'd like to use the equivalent of hide if field is empty...>something like: [hideif [fieldname]=]Try this: [hideif [fieldname]=]Sincerely,Ken GromeWebDNA Consultant Associated Messages, from the most recent to the oldest:

Re: Passing values - never mind (Kenneth Grome 1999)
Re: Passing values (Kenneth Grome 1999)
Passing values - never mind (Phil Herring 1999)
Passing values (Phil Herring 1999)

>I'm having trouble getting some extea name/value pairs from my shopping cart>to my invoice.>>I have a product that requires custom engraving, so I created three name>value pairs, [persname], [option1], and [option2] that take input from the>shopper on the results template. I can get the values from there into the>shopping cart line item no problem. But no matter what I try I can't get>them to the invoice.Anything that actually gets written to the shopping cart file is already there when the visitor gets to the invoice page. Either the data is NOT getting written to the cart file as you think it is -- perhaps because you're not using Header1 - Header40 field names or TextA - TextE field names, which are the ONLY available fields you can use to add extra data to your cart files, or else that data is in the cart file and you're not using those same field names to view the data ...>I've tried putting &[textB]=[persname] into the [setlineitems] context on>the invoice, then adding [textB] down in the invoice description, but that>doesn't work.That's because you should be using using &textB=[persname]. Remember, put the textB inside brackets when you're using a previously-created textB value for display or in a math calculation, but use the field name without the brackets when you're setting that value in the cart file.>Also, one more newbie question: Is there a way to use an empty field as a>value?Yes!>I'd like to use the equivalent of hide if field is empty...>something like: [hideif [fieldname]=]Try this: [hideif [fieldname]=]Sincerely,Ken GromeWebDNA Consultant Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: Passing values

1999

Top Articles:

Related Readings: