E-tickets not scanning (seeing ~xxxx) after ticket #
Hello,
Today is our first day scanning members in for timed entry slots. When a guest is presenting an eticket, it scans in with the ticket# and then a '~' followed by four characters. The ticket will not validate when the extra characters are included. If the ~ and everything after is deleted, the ticket will validate correctly.
According to this KB https://kb.blackbaud.com/articles/Article/73003 this behavior is expected and the work around is to change the scanning option to count as entered when scanned. I changed my settings to match, but this issue is still occurring. My preference would be to leave the scanning options as I had them (mark as attended when sold in daily sales on the day of the event) so that the box office does not need to take the extra step of scanning a ticket after they sell it at the window.
Has anyone else found a solution for this issue?
My next step is to attempt to program the scanner to drop all data after (and including) the tilde character so that it does not get sent to the validation box.
I will post an update if I get that working.
Today is our first day scanning members in for timed entry slots. When a guest is presenting an eticket, it scans in with the ticket# and then a '~' followed by four characters. The ticket will not validate when the extra characters are included. If the ~ and everything after is deleted, the ticket will validate correctly.
According to this KB https://kb.blackbaud.com/articles/Article/73003 this behavior is expected and the work around is to change the scanning option to count as entered when scanned. I changed my settings to match, but this issue is still occurring. My preference would be to leave the scanning options as I had them (mark as attended when sold in daily sales on the day of the event) so that the box office does not need to take the extra step of scanning a ticket after they sell it at the window.
Has anyone else found a solution for this issue?
My next step is to attempt to program the scanner to drop all data after (and including) the tilde character so that it does not get sent to the validation box.
I will post an update if I get that working.
1
Comments
-
We ended up just dropping the characters after the ~ symbol.
Not ideal but a workaround for the time being.
Since all tickets become validated with a timestamp this was a simple solution.0
Categories
- All Categories
- 6 Blackbaud Community Help
- 211 bbcon®
- 1.4K Blackbaud Altru®
- 396 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.5K Blackbaud Financial Edge NXT®
- 649 Blackbaud Grantmaking™
- 568 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 937 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.5K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 247 ResearchPoint™
- 119 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 239 The Tap (Just for Fun)
- 34 Blackbaud Community Challenges
- 31 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 785 Community News
- 2.9K Jobs Board
- 53 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)
