Share
ReportI am investigating an issue but am not that au fait with the inner workings of Dynamics CRM. So any help/advice appreciated.
We have an internal system that, on making a change to a type/field then invokes a change to the relevant entity/field in CRM. Upon this change in CRM (for certain fields) an API is called thats purpose is to replicate this change to a web application.
This API essentially retrieves an object from cache (original), and the object from CRM (new)... and for any differences it will update the cache object and update other related records.
The latter is not working and logging reveals that at point of retrieving the entity field (that i believe should have been updated) it is still set to the "original" value hence the program does not carry out any updates.
I havent done the development within CRM thats calling our API, so have little visibility, but shouldn't the CRM fields be updated instantly?
What is the best way of calling an API from CRM and guaranteeing that all CRM updates have been done prior to the API call?
As the API only fires on certain CRM field changes it is "seeing" a change in the CRM, presumably a database change triggering this?
Interrogating the CRM and field post crm plugin completion the entity is updated correctly, but seemingly not at the time of the API method call.
All responses (
Answers (
291,269
