SDK message errors got you down? We’ve got an alternative fix to take the stress away and those errors too! Let’s dive in!
As you can imagine, getting this error prevents the solution from being imported. There are some suggestions to create a solution with the offending process and modify the XML, but these may not work if you have custom actions.
The alternative fix we came up with was to completely delete all processes from the solution in the target environment and re-import. This may not be ideal, especially if you are pushing to a production environment, but it will let you get the latest solution before Microsoft releases a fix. Microsoft has stated that the fix will either be in UR3 or UR4.
Note: Always perform a backup of CRM before you attempt any changes!
Hopefully this helps you temporarily bypass any roadblocks with importing solutions. Remember you can always find great blogs full of tips and tricks for working with Microsoft dynamics CRM no matter what your skill level both in the FREE CRM Book as well as our website. Thanks for stopping by the blog today, and as always!