We have a set of SharePoint designer workflows that "communicate" with an event receiver on the list via changes to site column values. Adibidez, if a site column "SetDuedate" ezartzen bada eu arabera, gertaera hartzailea aldaketa detektatzen, epemuga bat kalkulatzen du, eta data hori esleitzen gune zutabe beste, "Due Date." We split things up like this because the event receiver can calculate a due date using complex business rules (asteburu eta jaiegunetan, enpresa kontuan hartuta) SPD benetan ezin bitartean.

Ko instantzia jakin batzuetan, we ran into a problem with this trick. Debugging all this is pretty difficult, baina etorri zen behin-betiko ondorioztatu dugu kasu batean dagoela (gutxienez), 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. Hala eta guztiz ere, koherentziaz zen lasterketak workflow hainbat urrats bat.

Hura aztertu ondoren, 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.

Beraz, … the Update List Item action did cause the event to fire. Beste alde batetik,, Elementu Gaurko ekintza-eremua ezarri ez.

Update zerrendako elementua erabili dut leku zein morea! It worked. [[ Guztira alde batera, Biolina jokatu dut ia for egunero 15 urte ]]

Honetatik, I tentatively believe that the "Set Field" Ekintza ez du ekitaldi hargailuak sua, 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, mesedez share iruzkinak.

</amaiera>

Nire blog Harpidetu.