Hi All,
I'm playing around with access areas on NScan before we begin using them. I have set things up in the TR NSCAN ACCESS AREAS table and TR NSCAN PROFILES. One thing I'm finding is that I consistently get entry denied if I don't have enough info in the TR NSCAN ACCESS AREAS table.
For example, if I just have area code, desc, perf str, start dt, end dt, max entries and prompt qty, I get entry denied on the scanner each time despite the ticket being for the correct perf and my dates corresponding to both the perf time and my scanning time. However, if I add in a price type ID, it works as I'd expect.
The scenario we want to have is to have tickets for a performance scan into a pre-performance event. So I would think that all I'd need in the system table is the perf ID but it isn't seeming to work. Since all perf tickets are valid, I don't want to add all price types to the access areas system table because that feels like overkill.
Thoughts? How much do you fill out in your Access Areas system table?
Thanks in advance!
Jenny
Hi Jenny,
Access Areas require that you provide at least one criterion from the options (Membership Level, Constituency, Attribute (with or without value), Price Type, Price Zone, List) to validate against. If you want to allow everyone attending a performance to get in, your best options are either
- A list of everyone who’s attending the performance(s), which you schedule to regenerate regularly so it’s up to date;
- Adding in all the price type IDs for all of the prices available in the performance.
If you routinely generate constituencies based on ticket purchases (such as Subscriber or Single Ticket Buyer) those constituencies would be another option.
Got it - thanks for your quick response, Jonathan!