This issue has been resolved as of the 19th of November maintenance window. Users will encounter this issue 1 more time for any comparison report generated containing changes from both pre and post the 19th of November.
After this the issue will no longer be present. Please use steps 1-3 to workaround this as needed.
We thank you for your patience while we worked to resolve this and apologies for any disruption or confusion caused.
issue
When comparing two revisions in ALM-enabled models, a workspace administrator may see that all of their modules, exports, dashboards and saved views are listed in the comparison report, despite many or all of them not having changed. These extra additions to the comparison report referring to "Fallback Context Policy" and "SINGLE" do not affect the sync and can be disregarded, however they do make the true changes within the sync more difficult to identify.
workaround
In order to see the correct set of changes for your sync:
- Revert the DEV model to the serial at which the source revision (where prod model currently sits) was created.
- Create a new revision tag.
- Now compare the target revision in DEV with this new revision to see what will really be in the sync.
- If happy with the changes listed, run the sync to PROD.
- Be aware that the comparison report will still show all the extra information when you step through the sync process here, but you can be sure that the comparison report generated from the DEV model in Step 3 contains the true changes.
If this workaround is not suitable in your use case, please contact our Care team.
