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.
There was an error rendering this rich post.
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…
