We have a set of SharePoint designer workflows that "communicate" with an event receiver on the list via changes to site column values. Per eżempju, if a site column "SetDuedate" is set to true by the workflow, the event receiver detects that change, calculates a due date and assigns that date to another site column, "Due Date." We split things up like this because the event receiver can calculate a due date using complex business rules (taking weekends and company holidays into account) while SPD really can not.

In one specific instance, we ran into a problem with this trick. Debugging all this is pretty difficult, but we came to the definite conclusion that in one case (inqas), the event receiver was not running all the time. In one step of the workflow, we would change the value of a site column and the event receiver didn’t appear to run. Madankollu, it was running consistently in a different step of the workflow.

After reviewing it, I noticed that the happy workflow step used the "Update List Item" while the other step used "Set Field in Current Item." Update List Item was updating the "current item." I’m not sure why we picked one over the other since they would seem to be doing the same thing.

Allura … the Update List Item action did cause the event to fire. Min-naħa l-oħra, the Set Field in Current Item action did not.

I used Update List Item in both places and viola! It worked. [[ Total aside, I played the violin for on a daily basis for almost 15 snin ]]

From this, I tentatively believe that the "Set Field" action does not cause event receivers to fire, at least some of the time.

This issue bedeviled us for weeks.

This is one of those "observed behavior" posts. I observed this happen once in a specific environment and I’m making some guesses as to why things happened as they did. If you have any insight into this one, please share in the comments.

</aħħar>

Abbona għall-blog tiegħi.