We have a set of SharePoint designer workflows that "communicate" with an event receiver on the list via changes to site column values. Për shembull, if a site column "SetDuedate" është e vendosur të vërtetë nga workflow, marrësi ngjarje zbulon se ndryshimi, llogarit një datë për shkak dhe i cakton atë datë për një kolonë faqen, "Due Date." We split things up like this because the event receiver can calculate a due date using complex business rules (marrjen e fundjavave dhe festave kompanisë parasysh) ndërsa SPD vërtetë nuk mund të.

Në një rast specifik, we ran into a problem with this trick. Debugging all this is pretty difficult, por kemi ardhur në përfundim definitiv se në një rast (të paktën), 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. Megjithatë, ajo ishte duke ecur vazhdimisht në një hap të ndryshme të workflow.

Pas shqyrtimit atë, 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.

Kështu … the Update List Item action did cause the event to fire. On the other hand, 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 vjet ]]

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, ju lutem ndani në komentet.

</fund>

Abonohen në blogun tim.