Price Layers, Price Templates and Ghost Rows

Hey there,

The 16-17 season was our first building pricing out with version 12, and we ran into some weird quirks that we continue to test and have issues with. 

We utilized a template for our single ticket pricing that we added after subscription pricing was already set, so we ended up with two layers of pricing - one for subscription pricing, and one for single ticket pricing. When adding the single ticket pricing layers through season maintenance, we found that the price types active in the subscription pricing layer ended up being active in our single ticket pricing layer, instead of showing as ghost rows as expected. This caused some confusion with some of our custom reports. 

We have double checked our single ticket pricing templates, and there are no subscription price types in there, so we don't know why those price types would show up as "active." We have done several test builds and keep running into the same problem, which makes me think we have an issue with the way we are building.

We ultimately inactivated those price types in the single ticket pricing layer by moving up the end date on the price type (in that layer only), so all is working fine right now, but we'd like to avoid this issue in future builds where we need more than one price layer.

For our next season build, we are discussing changing our business practices so we add single ticket price types at the same time as subscription price types, so all will be in one layer. This should help alleviate this issue in this circumstance, but it still seems odd overall. 

Any thoughts on what we could be missing? Thanks! 

Parents
  • Of course, the moment I go searching elsewhere for help, I figure out what was going on! It was a build issue, and we didn't realize that when adding a new layer, all price types from your first layer are selected (regardless of whether they're included in your template). Now we know we can simply unselect those, if they are not wanted, and avoid the issues we ran into. Thanks!

Reply
  • Of course, the moment I go searching elsewhere for help, I figure out what was going on! It was a build issue, and we didn't realize that when adding a new layer, all price types from your first layer are selected (regardless of whether they're included in your template). Now we know we can simply unselect those, if they are not wanted, and avoid the issues we ran into. Thanks!

Children