We discovered that during our upgrade to v12.5 that there was a conversion in the price layers that included a ‘Ticket Price 2’ with null date parameters. Although it did not change the prices, it confused our staff. We moved on, but have now discovered that the performances with this ‘Ticket Price 2’ layer show up in the data pulls with a lower ticket amount. The number of households are unchanged, and the revenue remains unchanged. Just the ticket number is lower by anywhere from 200 to 300+.
Has anyone else experienced this? Were you able to find a ‘fix’ for this anomaly?
Thanks,
Chi-Hsuan