Hi All--
We have been recently using Analytics to break out our unified daily postings between different types of transactions that our Finance department requires different data for - i.e. summary GL amounts for Box Office-related transactions, and constituent-level detail for Development. It is working quite well, but I'm trying to thread a very particular needle using the GL Segment pieces in a widget. I use these to break our GLs into individuated columns in a pivot table for output and upload into our finance software.
The hurdle I'm jumping right now is that in a six-part GL code structured like this:
#####-AAAA-AAAAA-AAAAA-AAAAA-# (where A is alphanumeric and # is a number, per T_DEFAULTS)
...not all of our segments are filled out on every GL Code. One segment in particular, is for 'Production', and our fees and payment methods are blank for these. So a complete GLCode might look like:
23500-TALK-LOVE -TICKS-TSALE-1 for a production
and
43610-GOS - -TFEES-FACF -1for a fee
I've discovered that when there is a break in the GL code as written, the spaces are read as non-alphanumeric characters, and so they become the delimiters for the GL parts 1-10 in Analytics, throwing a real wrench in my plan to make life easier for Finance. I confirmed this is expected behavior with a ticket, and I'm turning to the forums as a last resort before exploring custom elements or (gasp) requiring a text-to-columns step in our processing.
Are there any brilliant pieces of code out there for a non-SQL resource like me to use which might help me force my widget to define the segment delimiter as '-' and ignore spaces? Any advice would be very appreciated!
Best,
Michael B
Hello Michael! This is Iliana with Tessitura Network Support. We’re happy to assist you with this post. I can see from our records that you’ve also created a Support ticket where we’re working with you to find a resolution to this question and it looks like there was some resolution but not all of it. I will go ahead and ping the team in the ticket to connect with you again and see if we have found more information on this.
Thank you,
Iliana