Hello -
We've converted our Test environment to v12 and I found a minor issue which I think I have fix for but wanted to run it by folks smarter than myself before doing it: v12 creates it's price layers via designations on your price maps. However, we have two fees - each a set amount and different from each other - embedded in our ticket prices with the same designation (since it's never really served a serious purpose before). These are then converting into v12 as "Fee Layer 1" and "Fee Layer 2".
However, depending on how the price type was built, sometimes the fee 1 price map comes first (for, say $1) and sometimes the fee 2 price map comes first (say $2). This means that the fee layers in v12 are not consistent and if I rename the layers things go a bit sideways. Fee 1 (for example) should always be $1, but in v12 pricing for past shows sometimes the first fee layer is $1 (correct) and sometimes it's $2 (the other fee price map).
I was thinking if I create two new designations and recode all the fee price maps via SQL to the new designations they would convert more cleanly. However, I'm unsure of any unforeseen repercussions: Can I just run a small update script on T_PMAP to recode the fees to the new designations without hurting anything in, say, T_TRANSACTION or any other critical table?
Any advice is helpful. Thanks all!