Share
ReportHi, I'm new to the world of CRM and have just deployed my first release.
The solution that I exported from Development to Production only contained a few basic javascript, form and option set changes to keep things simple for my first release. The solution strategy in place at my employer is to keep everything bar plugins in one solution. What this means is that 100+ workflows get deployed every release despite making no changes to them.
After deploying a large number of these workflows were unable to reactivate after being overwritten, due to GUID issues relating to Queues that they were referencing and Word Templates that they were using.
After experimenting I have been able to sort out the GUID issues for the Queues by using the Configuration Migration SDK tool to export Queues from Production and import them into the Development instance. One or two lookup field references failed on import, but the main result is that the Queues in Development now have the same GUIDs as Production, so hopefully these will deploy in future without issue.
The problem I am struggling with is how to get round the GUID issue for the Word Templates. These are used by a number of work flows and since they are lookups they all have GUIDs. Since the GUID reference in the development area differs from production, then the workflow is unable to reactivate after deployment. It's simple to fix as it just involves opening the workflow template step, saving it and then manually activating. However, the sheer number of workflows makes this an onerous task so I'd rather it didn't happen!
Any suggestions would be most welcome.
Matt
*This post is locked for comments
All responses (
Answers (
11,323
