Thursday, 15 April 2010

Why does Dynamics CRM 2013 plugin fire twice on owner change? -



Why does Dynamics CRM 2013 plugin fire twice on owner change? -

i have simple plugin custom entity set trigger on update of custom entity. registered in post operation stage. have noticed unusual behaviour when create changes owner field of record in add-on other standard fields (e.g. text boxes, dates etc).

the plugin fires first time , attributes come across in image regular fields. owner field not come across.

the plugin fires again, depth property of context still one (i.e. plugin not getting triggered changes made in plugin code). in run of plugin, attribute come across owner field.

my theory because owner fields 'special', crm doing 2 different requests - 1 alter regular fields, , request changing owner via assignrequest. however, cannot find 'official' documentation behaviour.

can explain why happening?

i running dynamcs crm 2013 ur2

the update event fires during assign event. if assignment takes place plug-in execute. same true setstate - if activate/deactivate record update event takes place. these items not documented in sdk.

a practice utilize attribute filtering on update plugin fires fields concerned - will, assuming isn't looking @ owner related fields, avoid firing twice. if have logic specific record ownership set in plugin registered on assign event.

dynamics-crm dynamics-crm-2013

No comments:

Post a Comment