• Replies 3 replies
  • Subscribers 415 subscribers
  • Views 20 views
  • Users 0 members are here
Related

Ticket Data Element Printing Issue in v12.1

Christopher Short
$organization

Good afternoon!

We're currently testing v12.1 in hopes of going live within the next couple of weeks and have run into an odd issue with a few data elements not printing out where they are expected to be based on the current design.

Specifically the Perf. Date (used 4 times on the ticket) and the Perf. Begin Time data elements in the Performance Data Group.

These 5 elements are all on the same row, and spaced across the face of the ticket horizontally.

Perf. Date (Mask dddd; justify left; location 275*195)  Perf. Date (Mask mmm; justify left; location 275*384)  Perf. Date (Mask dd; justify left; location 275*457)  Perf. Date (Mask yyyy; justify left; location 275*509)  Perf. Begin Time (Mask h:mm AM/PM; justify left; location 275*611).  All of these elements are using Font-3.

These are the only elements that are not rendering in their expected location on the printed ticket.  They are covering the entire length of the ticket.

Is there something that I've missed in the documentation?  Has anyone else encountered this in v12?


Thanks!
Short 

Parents
  • $organization

    Hey Short,

    Sadly, we did not have those issues when we moved to V12. If everything appears to be fine when looking at the design element properties I'd suggest opening a help ticket.

    But on a somewhat related note, I thought it was interesting that your dates are split into 4 elements. We have our date as one element with a mask of:
    ddd, mmm dd, yyyy

    And then on the ticket stub with a mask of: mm/dd/yy

    I guess I never thought about splitting it up into separate elements. Is there a benefit to that method that I've never considered or is it all the same stuff in a different pile?

  • $organization in reply to Beth Hawryluk

    Thanks, Beth!

    To be honest, this is a design that I inherited but it has worked flawlessly for the last four years.  I'm not sure why it was broken up into 4 separate elements, having tested your set-up I think that it's all the same stuff in a different pile.

    Curious, what value did you use for data length?  I set my test design up with 22 and it seems to work like a dream!


    Cheers!
    Short 

  • $organization in reply to Christopher Short

    My data length for that element is currently set to 17. It's always worked just fine for us!

Reply Children
No Data