Hi,
I'm wondering if anyone has encountered any problems with moving their Ticket and Performance History when they move transactions. I'm hesitant about configuring this setting because if we moved the ticket and performance data to an individual or household, then I'm assuming that the tickets we already printed will error with N-SCAN, since the tickets will now be under a different constituent ID.
Am I worrying over nothing? Has anyone using N-Scan seen any issues with moving their Ticket and Performance History to or from household records?
Thanks,
Tiffany Evans
Database Coordinator
Huntington Theatre Company
Tiffany,
We regularly move transactions to household accounts because of merges and creating households on a daily basis. I’m not aware of any issues with tickets scanning. We’ve been doing this since we went live with v11 last August and I haven’t heard a peep from the FOH staff about tickets not scanning.
Teresa L Dean | Tessitura Systems Director | AT&T Performing Arts Center