Hey everyone,
First, a little background on why I'm asking. Our theatre uses CSIs primarily to notify house management about patrons with mobility issues. We are currently seating our 2019 season (we operate on a calendar year), and are adding in CSIs for patrons that have these issues. My team is going through and adding seat number and the nature of the patron need manually to each of the 6 performances included in our season. When we attempt to add in a CSI to a Package, the CSI then shows up when we run a CSI report for ANY performance. Our inability to just make note of the patrons needs and seats for the whole season at once essentially increases the amount of information we need to enter in by about 600%
So my question: is this Pack-based CSI showing up on every order because we are entering the information incorrectly or because we are pulling the information incorrectly? Or is it even possible to add a CSI across multiple performances in a package so that the same CSI does not show up in performances NOT associated with that package?
Boy, I hope that made sense. All help is welcome, let me know if there's any more info I can give to help solve this. Thank you all!
Same exact issue here; you're not alone. My approach has been to build a utility that lets you copy a CSI to all of the individual performances within an order. That way it's only entered once, but it still gets pulled by house management for each individual performance. It's a little messy on the constituent record, but I think it's okay for that to be the case; it's accurate, after all.
Happy to share the utility on the Bitbucket repo if you would find it helpful.
If you could share it with me that would be fantastic!
Got it all wrapped up for you! https://bitbucket.org/TN_WebShare/copy-csi-to-order/
If you don't already have access to the code repository (if the link looks broken), you can request it here: https://www.tessituranetwork.com/Support/Resources/Developer
Thank you! I'll begin experimenting with it. Much appreciated!