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 am attempting to connect to an azure SQL database vis at the MSSQL connector in data orchestrator but am having issues and I believe it is due to hyphens in database name (which is a fairly standard naming convention I will note!) Example below (fake credentials) - has anyone else encountered similar and is there a way…
Hi, for some reason my shipping costs are the same over every month and I don't know what to do to fix it.
Hello folks, Does anyone know how to work around the Polaris limitation of using the Formula or Ratio summary method alongside the Closing Balance within the same line item? I have a Business Unit list where the total (All BUs) must display the Corporate (1 of 20 leaf items under All BUs total) number of Unique Customers.…
