If anyone on v11 is still able to monitor attendance through NScan to receive email notifications when target patron tickets are scanned, could you please let me know if you had any problems after upgrading to v11 and how you're making it work now?
We use the NScan Monitor List attribute to track attendance. In v10, you'd choose NScan Monitor List as the attribute and then in the attribute value field you'd have a drop down to select the list you wanted to monitor. In v11, the drop down is gone. I've tried typing in the list number, but that doesn't seem to trigger the notifications. We opened a help ticket and were told that this is the first time anyone has notified the Network of this problem. I'm also unable to get the NScan Monitor Individual function to work, either.
Any help you could offer would be greatly appreciated.
Thanks!
Amy
Hi Heather,
It was number that wasn’t working for us. We switched it to string and the dropdown is back and it’s working again. Just figured it out this morning. Thanks for weighing in!
From: Heather Kraft [mailto:bounce-heatherlaidlawkraft3507@tessituranetwork.com] Sent: Friday, November 09, 2012 12:12 PM To: Amy Finch Subject: Re: [Tessitura Ticketing Forum] NScan Users - monitor attendance notifications not working in v11?
Ugh. Ignore what I said - it was actually changing the Edit Mask that made the dropdown work - however, I didn't check that it would actually save, and it doesn't now. Doh!
So belay that flip answer there. I'm still going to test the monitor attendance and will report back.
From: Heather Kraft <bounce-heatherlaidlawkraft3507@tessituranetwork.com> Sent: 11/9/2012 10:48:58 AM
Hi Amy -
There's a really quick fix to the drop-down - in T_KEYWORD make sure your Data Type for NScan Monitor List is set to Number. We did discover that, but I thought it might have been something I set up strangely in my own system so didn't report it.
I'm actually not sure if anyone is currently being monitored through NScan at our organization - the lack of complaints could either mean it is working or no one is currently doing it.. I'll have to do a test tonight and report back to you!
- Heather
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Hey Amy -
Glad it works! Our Edit Mask was also tweaky for some reason - just in case other people stumble on this particular problem, this is what seems to be now working (at least for attribute setup) for me (and it does actually save):
T_KEYWORD: NScan Monitor List
Data Type: String
Edit Mask: None
Detail Tbl: TX_CUST_KEYWORD
Detail Col: !.key_value
Ref Tbl: VS_LIST
Ref IdCol: List No
Ref DescCol: List_Desc
Ref Sort: List_Desc
Use for List: Attributes
Multiple Value: Checked