Skip to end of banner
Go to start of banner

The ID of a configuration object "X" deployed with CMJ is differs from the id of the same object on source

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Problem:

Certain scripts or other custom configuration that is not supported by CMJ rely on configuration objects' ids and these functionalities don't operate correctly after deployment with CMJ

Cause:

CMJ does not have control on configuration object ids, as they are generated by the underlying framework used for persistence. 


Solution:

It's recommended to refer to configuration objects by name whenever possible. 

CMJ also provides a setting called "Persist deployed snapshot to current system native ID mappings", available in the General Settings page https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/33456130/General+Settings
When it's enabled, the add-on generates a mapping of the ids coming from the snapshot to their counterparts on target instance. This mapping can be used to update the ids post deployment manually or through a script.

  • No labels