When an ALM sync is incompatible, is reverting prod to last revision an acceptable way to fix the compatibility issue?
The easiest way is to get rid of your dev model and create a new dev model using production copy. But consequences of this approach is that you will loose all your development done in the old dev model and you need to do it again in the new Dev model. If that's an acceptable trade off, it's simplest approach.
Otherwise reverting the production model, might impact production data loss!
Sure that is 1 option.
However, I see another option in this article - 'Navigate to the Revision Tags tab [in prod], and if structural changes have been made, the “Revert to Last Revision” icon will be bold.' Select "Revert to Last Revision".
This works if structural changes are made in Prod, but no revision tag is set yet.
Reverting prod to last revision is necessarily not a good thing since data loss is a possibility , so it is possible to create a new dev from the production and then maintain the sync
That could be an option. However, development from dev model would need to be redone.
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…
Anaplan Champions! The Community team just posted this announcement that certification badges may not be showing up on your profile probably until next year. Rest assured, you will get credit once you complete and pass the exams. https://community.anaplan.com/t5/Blog/Badges-Back-Soon/ba-p/123385
