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

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

Turned off automatically add new items in a line item subset.
Added a new line item to the module where the line item subset is driven from.
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.

Comments

Quick Links

New ideas

Assistance Required for Understanding User License Roles at Tenant Level - Anaplan
Team - As per my understanding, user roles should work as described in the table below, but it is not working as expected. Our expectation is to assign users to a read-only role to restrict their access to a specific model, instead of creating user roles within the model. Any insights would be greatly appreciated. Thank…
Text input on total level
Dears, We would like you to enable text input on text summaries. Could you please consider adding “text input” button for text type summary method? This will help a lot for better navigation, for example when commenting data on total level like P&L total figures.
Ability to Generate Management Reports based on a Hierarchy Chart
We currently have a requirement, working with a very large Bank on their Workforce planning use-case to view their Organisational Hierarchy in a Current and Proposed state. The UX view of the Hierarchy Chart works well, even with very large volumes of data. There is also a requirement to have a Management Report that…