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 '\'