Share
Report
5From initial investigation it seems that when we update a description field for incident entity , event is fired by solution Plugin . But it seems that DCRM takes time to update the value in backend database due to which when we retrieve (using WebAPI) the updated field as soon as we receive update event message, we get older values.
The issue is seen in Incident (case) entity for description attribute and in plugin registration tool we added the step "DynamicsCRM.Plugin.EventListenerPlugin: Update of incident" and event pipeline stage is "post-operation" and "synchronous" mode.
In the solution Plugin code, im using Target from InputParameters to fetch for updated values and for older values we use pre-entity image data.
Why there is a delay in update for some attributes as mentioned above for "description in incident entity" for Event pipeline framework and Web API service. Though the delay might by in milli-seconds , we need the data to be uniform across all the services.
I have summarized my questions as below. Please answer them.
- Am I missing out any thing to check in solution plugin code which gets triggered before the commit of data? Please let me know.
- Can you also please confirm, if the post-operation triggered only after commit operation of data for plugins?
- And also there is no data coming for context Output parameters object for update event . How can I confirm if the data is committed and if I only depend on the context InputParameter Target value.
NOTE: Below issue is seen Dynamics 365 Online server only non in On-Premises Dynamics 365 server.
All responses (
Answers (
