Hi everyone -
I have a support ticket open for this issue as well, but figured I'd ask you all as well!
I am attempting to do some test rollovers in our TEST environment and am running into issues. First, I updated the rollovers set for this current season to roll into next season (FY20 into FY21) and when I ran the rollover sets, it was showing me the rollovers from last year (FY19 into FY20).
This morning, I created a new rollover set in case that was the issue, but when I attempted to run it I got the following error:
Has this happened to anyone else? I am 99% sure I have all the setup correct (all packages, performances, price types are in the selected rollover MOS and dates are active)
Thanks in advance!
Kari
To add to the fun:
I tried a different rollover rest and now get this fun error message:
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_T_SUB_LINEITEM_TR_PRICE_TYPE_original_price_type". The conflict occurred in database "impresario", table "dbo.TR_PRICE_TYPE", column 'id'
Clearly, the system does not want me to do any rollovers. This happened for a rollover set that is using the price mapping table and for a rollover set that is just copying from previous. Double checked that all my source price types are available in the target packages, so I think it's just time to wait for Support to answer my ticket.
Probably.
The only thing that occurs to me on that is, is there any chance that you have two different price types with the same description and chose the wrong price type ID (but correct description) in the mapping table? Unless I am misreading things, that foreign key would imply that the price type ID it is trying to assign to the new orders is incorrect in some fashion.