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.
I have 2 lists used in modelling, In Input module I'm using subset of territories from Country List and subset of Regions from Flat list. But in Output module,Its reversed, I'm using subset of regions from Country list and subset of territories from flat list.How to derive the numbers from input to output module. I do have…
This shows all comments across all data to all users with access to the UX page. This is not appropriate for any UX which might contain security access sensitive data. Comments on grids and cards ARE security dependent. That works fine. But anyone with access to the page can open this Summary Panel and see ALL comments…
If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote. Thanks!
