Hello! we have all of our current facilities listed comma-delineated in TR_NSCAN_PROFILES in the Facility Str field, which I expected from the help documentation to mean that all performances in those facilities should automatically be imported on the scanner devices, without any extra setup; but in actuality, I'm having to log into the Admin settings in the NSCAN app on the device and manually enter the Perf IDs in the Performance field on the app. We're not such a crazy busy schedule that it's impossible to do this manually, but I'd rather the table worked as advertised, anyone have any tips on troubleshooting and this table?
Hi Erin!
In the NSCAN app, in Admin Settings > System, is the "params from host" setting set to on or off?
It's on!
Are there spaces in-between the facility ids? Do you have any other settings filled out for the profile? What was your indication on the device that you need to manually input the performance ids?
No spaces, should there be? in the table, the Perf Str, Entry Point, Access Area, and Customer No fields are all blank; the Allow Seat Check and Allow Monitor fields are set to 'Y'.
The performance IDs from last season's performances were still filled in on the devices, so I replaced them with the current Perf ID and that made the event scannable.
Are last season's performances still listed when you reload the profile?
reloading the profile clears the Performance field, and it gives the "Event not authorized on this device" error again.
Do you by any chance use the door open and door closed dates in ticketing setup and have the use perf door times set in T_DEFAULTS? If you are trying to scan a ticket outside the times entered there then it would give this error, I think.I'd also check that the date/time on the scanner is set to the current date time and that the facility id is definitely saved in the system table for each scanner.
We have perf door times set to 'Yes' but we don't actually have door times set on the events - they're all the blank 00/00/0000 setup. I did add door times to one event to test, and that didn't seem to make a difference, I still got the error. Setting it to No in Defaults doesn't seem to matter either.