Hello,
I am putting together a new receipt format for our Gift Certificates. I would like to add a data element for expiration date. The expiration date should be one year from the original sales date of the gift certificate.
There is a data element called GC Original Date which works great for printing the original date of issue, but how do I now add one year to that date and then print it on the ticket? Is there a way to sneak code into the Mask format that will allow me to adjust the date by a year?
This is for printing to the ticket printer. Once I get this figured out I will move on to the form design to print the same information with Gift Certificate Batch Printing report.
Thanks in advance for your help!
A work-around if there is not a solution is to hardcode: Gift Certificate expires 1 year from this date - <insert today’s date>
If there is a solution…I will be implementing this one!
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Jared Mollenkopf Sent: Friday, November 19, 2010 9:13 PM To: Becci Brace Subject: [Tessitura Ticketing Forum] Modifying dates in Ticket Design
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
We print date issued on our certificates and then print "Expires 5 years from date of purchase." for the expiration date.
Just a quick reminder for everyone to check their state law regarding gift certificates relating to expiration dates. Many states have recently uipdated specific requirements as to when gift certificates are allowed to expire. Fewer and fewer states are allowing a 1-year expiration. In our state (Michigan) gift certificates must be valid for at least 5 years.
Have you looked in the LP_TICKET_ELEMENTS procedure? I believe you can create up to six different cases in that procedure that will return your own information to the specific ticket element (Data > User Defined Element).
We currently use the GC Original Date Data Element and then mask it with dd mmmm 2011 (we are currently changing the date in January every year to reflect the next years date), as we have not yet been able to get the year part of the date to work as conditional masking.
Caryl
This might be of help/use, but I just realised that I had a custom ticket element that I made ages ago to calculate the date to be 12 months from the order date.
The date is formatted as Nov 23, 2011 … so it looks a little prettier than the standard date. You can change it to other formats by changing the 107 in the convert function. SQL help is a good source to find out what the others are.
Of course like with anything, try this out in Test first just to make sure that it is what you are after.
If @ude_no = 6 and @customer_no > 0
select @ude_value = convert(varchar,DateAdd(mm,15,a.order_dt),107) from t_order a
where a.order_no = @order_no
Cheers
S.
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Caryl JonesSent: Monday, 22 November 2010 8:52 PMTo: Sandra AshbySubject: Re: [Tessitura Ticketing Forum] Modifying dates in Ticket Design
From: Nathan Campbell <bounce-nathancampbell1231@tessituranetwork.com>Sent: 11/22/2010 12:52:06 AM
Hi Jared,
We use the GC Original Date data element and then use the following mask to calculate the 1 year expiry date.
String(date(val), 'mm/dd') + '/' + String(year(date(val))+1)
Thank you, everyone, for all of the great input. I have entered the masking provided by Michele and it works perfectly.
Todd, thank you for making the reminder for everyone to check local laws. This is important because the rules can get very specific, and they can change from year to year.