What's everyone doing for their ticket headers in V11? Noticed today that households print the household name (ie, Tom Jones Household) for the data element "Customer Name1". Are you using Salutation here?
I thought we where using salutations but it looks like we have made the same mistake!! We will have to use customer salutations going forward
Yep, we've switched to Salutation1 from Customer Name1 due to the 'Household' issue as well.
- Heather
I'm finding that the our standard Header/Envelope seems to have a character limitation of 28.
For instance, in my first test print the header for my order printed, as many have found out, the Household name:Christopher and Rachel Short (Household)
However, the Salutation has 33 characters, which would make for an awkward looking header that would read:Mr. and Mrs. Christopher L. (Short)
Items in parentheses do not print on the header.
We're also finding this problematic in our general ticket design as we have previously printed LastName1 on the tickets and that is also pulling the household name rather than the Last Name. The salutation wouldn't really work here as we were hoping to save some real estate. Does anyone else employ these items in their ticket designs?
Thanks!Short
Hi Chris,
We've run into the same issue with Lname1 on the Ticket. And since we don't have the real estate to print the full salutation, I had hoped to find a new canned element for 'Sort Name'. Unfortunately, that doesn't exist so we have allocated one of our precious UDEs to get the portion of sort_name before the '\'
We had the same issue so we changed the element on the ticket header to a “User-Defined Data Element”. The online Tessitura help points to the LP_TICKET_ELEMENTS procedure which you can customize to return the A1 (formerly N1) name using the VB_CUSTOMER “bridge view”. The code in LP_TICKET_ELEMENTS looks like this:
IF @ude_no = 1 AND @customer_no > 0
SELECT @ude_value = ISNULL(fname + ' ','') + lname
FROM dbo.VB_CUSTOMER
WHERE customer_no = @customer_no
I’m open to alternative suggestions but this works for us since it’s what we’re used to from v10, and more importantly, it fits on the ticket.
Michael
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Christopher Short Sent: Thursday, June 07, 2012 6:58 PM To: Michael Reisman Subject: Re: [Tessitura Next Generation Forum] Ticket Headers
For instance, in my first test print the header for my order printed, as many have found out, the Household name: Christopher and Rachel Short (Household)
However, the Salutation has 33 characters, which would make for an awkward looking header that would read: Mr. and Mrs. Christopher L. (Short)
Thanks! Short
From: Heather Kraft <bounce-heatherlaidlawkraft3507@tessituranetwork.com> Sent: 5/2/2012 6:41:53 PM
You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!
We had the same issue too. Info here was very helpful. Thanks :)
We used following to get sort name into one of the user defined ticket elements:
select @ude_value = sort_name
from T_CUSTOMER
where customer_no = @customer_no
Thats the last of our user defined elements used up.
Would be great if the sort_name could be added to the standatd list of elements.
ta, Dara
We also switched over to sort name, which worked great for just the name, but not on our custom ticket header.
On our custom one - we replace the first name line with a name in the notes area after a certain character string - so that we may be able to do a pick up under a different name. Previously it was pulling last and first names separately but with sort name it is a combined field - so the special code we have is getting lost.
And I just can't see the solution - I am having a serious case of the 'Mondays' :-)
if @ude_no = 1 and @design_type = 'H'
begin
-- declare @notes varchar(255)
select @notes = ord.notes
from t_order ord
where ord.order_no = @order_no
if substring(@notes, 1, 2) = 'xx'
declare @end int
select @end = charindex(';', @notes) - 3
if @end <= 0
select @end = 30
select @ude_value = substring(@notes, 3, @end)
end
else begin
select @cust_type = cust_type from t_customer where customer_no = @customer_no
if @cust_type in (1, 6, 11)
select @fname = isnull(fname, fname2),
@lname = isnull(lname, lname2)
from t_customer where customer_no = @customer_no
select @fname = isnull(fname2, fname),
@lname = isnull(lname2, lname)
select @ude_value = rtrim(@lname) + ', ' + rtrim(@fname)
------------------------------------------------------------------------------------
if @ude_no = 4 and @design_type = 'H'
select @ude_value = ''