Nobis statuto de SharePoint excogitatoris workflows quod "communicare" with an event receiver on the list via changes to site column values. Verbigratia, si a site agmen "SetDuedate" vera posuere workflow, eventus susceptor detegit quod mutatio, reputet debitum date et assignat quod date ad aliud site agmen, "Due Date." We split things up like this because the event receiver can calculate a due date using complex business rules (accipiens weekends et comitatu festis in propter) dum SPD vere potest non.

In specialis puta, we ran into a problem with this trick. Debugging all this is pretty difficult, hic autem ad id determinat (saltem), 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. Autem, est currit constanter in a diversis gradum workflow.

Post recognoscens eam, Animadverti quod beatus workflow gradus usus "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.

Ita … the Update List Item action did cause the event to fire. SED CONTRA, in pone Field in Current Item actio non.

Ego Update List Item in utroque et hyacintho! It worked. [[ Totalis seorsum, Ego lusit in vitae enim in a cotidie basis fere 15 annis ]]

Ex hoc, Ego relatione credere quod "Pone Field" actio non faciat eventus receptatores ad ignis, at least some of the time.

This issue bedeviled us for weeks.

Hoc est unum eorum "observavit moribus" 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, placere participes in ineo.

</finem>

Scribet ad mea blog.