If possible, I often like to code against a standard ‘vanilla’ AX implementation if possible. It makes it easy to debug functionality and check things – as I said, when possible. Workflow coding seems to lend itself well to coding against a standard out of the box AX machine. But I saw the strangest error while I was coding some workflows on the Microsoft Dynamics AX 2012R2 sample machine. After doing a full Update (aka full generation) with the cross-reference tool, the workflow add-in tool wizard would no longer come up and kept giving FormRun errors.

Quickly, I went through the standard troubleshooting:

1. Cleared Cache on the Client – No fix
2. Cleared Cache on the Virtual Machine Server – No fix
3. Ran a full CIL Generation – No fix
4. Restarted the AOS on the virtual machine — No Fix
5. Restarted the Virtual Machine – No fix
6. Ran a full compile followed by a full CIL generation – FIX

Interesting. One of these days, I’ll have to dig deeper when I have time to figure out why full compile fixes this, but it is amazing how many times you must fix things with a Full Compile in AX. I just hate doing it because of the downtime, but it is what it is.