This issue was fixed in the July 19, 2025 release

issue

When comparing two revisions in models enabled within Application Lifecycle Management (ALM), a workspace administrator may see that some of their modules, exports, dashboards, and saved views are listed in the comparison report, even though many or all of them haven't changed. 

These additions to the comparison report that refer to "Page Context" changing from "-" to "SINGLE" don't affect the sync, and you can disregard them. However, be aware that these additions will make the true changes within the sync more difficult to identify. 

workaround

In order to see the correct set of changes for your sync:

  1. Revert the DEV model to the serial number at which the source revision (where the prod model currently sits) was created.
  2. Create a new revision tag.
  3. Now compare the target revision in DEV with this new revision to see what will really be in the sync.
  4. If you're 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. However, the comparison report generated from the DEV model in Step 3 contains the true changes.

If this workaround isn't suitable for your use case, please contact our Support team.