custom workflow gets deactivated when importing solution because workflow property GUIDs are different for different CRM environments

[arjun-bhatia]

Hi All,

I am having an issue while importing a solution because the custom workflow gets deactivated. The reason this is happening is because workflow property GUIDs are different for our different CRM environments. So when moving the solution from one environment to another, the destination environment does not contain that GUID and hence the workflow gets deactivated. Is there a way to update the properties/inputs parameters of a workflow through the build pipeline tasks? Thanks in advance!

[WaelHamze]

@arjun-bhatia

Below are some options on who you might be able to overcome this

1. Ensure Guids are same through well define reference data management process. Use can use config migration tool to achieve us.
2. See if you can remove the depending on Guids from Workflows by looking up records dynamically
3. If you are using solution packager you would run a powershell script at some stage in your pipelines to change the Guid values before you generate the solution zip