MS Dynamics CRM Usability

Our primary focus is on Microsoft Dynamics CRM usability & training issues, but other issues will appear from time to time.

We’d love to hear from you. Please take a moment to sign up, and let us know what you have to say.

View all Biz IT Blog articles...

CRM 4.0 Rollup 3 AsyncRemoveCompletedWorkflows side effect caution

June 26, 2009

Microsoft's fix to control the sizes of async operation base and workflow log base tables can have unexpected results...

As part of implementing Microsoft Dynamics CRM 4.0 roll up 3, there are several patches which can only be implemented manually using regedit. When Microsoft implements a hot fix this way, it means they have concerns about possible effects upon your implementation.

We have literally hundreds of workflows designed to streamline our operations, so the files to store the history of this were getting out of control. Yesterday, I implemented the manual regedit edit configuration as specified by article 968755 which relates to how to keep your async operation base and workflow log base tables from getting too large.

Be aware, the downside of this hot fix is that after each workflow completes, you will no longer have any history of executed workflows either in the system jobs folder and settings or in individual entity navigation pane workflows folders. This will make it very difficult to diagnose workflows. Since I use this history rather extensively to track our complex workflows, the solution turned out not to work very well for us.

I ended up having to turn it back off again. I guess it’s worth it to me to keep the history of the workflows

See the update rollup 3 knowledge base article 961768 and Microsoft knowledge base article ID 968755 for more information about this.

Steve Noe, MCT