Migrate Line Item Subset changes as an earlier step when using Revision Tags

AndrewHall

I recently encountered an issue where I had performed the following steps in my development environment:

1. Turned off automatically add new items in a line item subset.
2. Added a new line item to the module where the line item subset is driven from.
3. Set the new line item to have the data type of No Data.

When migrating to a deployed test model, the system appeared to migrate these in the order 2,3,1 meaning that the sync failed as in between steps 3 and 1, it was trying to add a line item with the format of no data to a line item subset.

Not sure if anyone else has experienced similar behaviour, there is obviously a work around but it was just tedious continually taking revision tags in the right order to get the desired outcome in the deployed model.