Hello!
We’re having some issues with ticket counts in Analytics. Way back, before Analytics existed, the ACO started using a copy of the price category ‘Ticket Price’ (ID1) from TR_PRICE_CATEGORY.
Unfortunately, Analytics only counts price layers using the price category ‘Ticket Price’ (ID1).
We have tried two different ways to remedy this in our dashboards:
The results are unsatisfying, to say the least. Ticket count is under reporting, RSUM SLI ID is over reporting.
Going forward, we’re hoping to simply switch back to ‘Ticket Price’ (ID1). I’m currently investigating this with our Finance department, taking into consideration their various custom reports.
Any suggestions on how to solve this current / historical mess would be greatly appreciated!
Thank you,
Carola
I bet your over counting is from the sub line-item status'. Do you use multiple pricing layers? If so, you must use the unique SLI ID along with the SLI status. It all depends on what SLI status' you want to count.This also brings up the issue if you use multiple pricing layers, you also have to use the # of unique SLI ID instead of ticket count. As a rule, I always compare the ticket count to the # of unique SLI ID numbers. I now always do this in case there is an oddity with setup.Anyway, I'd suggest using a filtered value. You'll need to play around with the filter parts to see if you can get it to the correct numbers.Sample:Syntax:
(<aggregation> , [Filter1], [Filter2], [FilterN])
We use this method to get at our potential group sales orders that have not yet been paid for. In this example, there is a large difference between tickets paid for and what the potential sales currently show.
Hi Neil,
This makes a lot of sense. I will give it a go and let you know what I find.
Thank you very much!