Revision Pull Conflict - Changed Connections
I have an integration in the sandbox environment that is used for testing and connects to test environments in our other systems. This flow was cloned to production and has been in use for a few days. I have successfully made many edits in sandbox that have pulled to production without any issues.
Yesterday, I changed the connections in both the sandbox integration and the production integration. Now, when I attempt to pull over some new changes from the sandbox, I receive the conflicts noted below. It says the conflicts are that the _connectionId is different. Of course, they are different because they each connect to a different environment in the other systems. How can I get around this?
1
Comments
Hi Michael Gantt,
Ideal way of updating connections is to have the new connections added to the integration in Sandbox and then use 'Pull' in Production integration to have the new connections added to the Production integration while merging the changes from Sandbox integration.
When you update the connections (or any other dependent objects) in both Sandbox and Production integrations independently, the system understands that the state of both integrations is altered and so shows conflict.
For you to fix this conflict now, I would advice you to revert the Production integration to the state before the connections are added and then pull the changes from Sandbox integration. With this, you will not see the conflict and also see an option to add new connections.
Do let me know if you need any further assistance on this.
I understand now and that worked. Thank you for the quick response!
Please sign in to leave a comment.