Dynamics CRM entity status weirdness

▤ Summary

Since upgrade of CRM Online to 8.2, we have noticed some strange issues around workflow triggers that are supposed to be fired by the change of a record status. We trigger the workflow in a couple of places – in C# code that runs during various automated operations, and in Javascript in response to a manual button click. As none of this fits with documentation we assume it is an obscure bug in the platform Microsoft have made changes to the way entity status interacts with processes. The Microsoft recommendation is that all code which changes record status should do using updates, not the deprecated SetStateRequest UPDATE: however from our later tests we consider SetStateREquest to be the safer option on the IOrganizationService For workflows which are set to trigger on “Record status changes” there appears to be inconsistent behaviour depending on the source of the update (SOAP via the IOrganizationService, or directly to the newer REST API ) From our tests, any workflows which are triggered from “Record status changes” should be modified to fire on “Record fields change”, filtered down to just the status field. Worflow steps created in the Workflow Designer which call “Set record status” still work, and will still fire triggers that have been modifed as above

▦ Linked Companies

Microsoft

$1B+