Tech Support > Microsoft Windows > Windows CRM > Weird CRM callout behavior
Weird CRM callout behavior
Posted by jfmenard on March 8th, 2005


I'm creating a post callout object for products in CRM. PostCreate an
PostUpdate work fine, but when I delete a product in CRM, th
PostDelete is called and works fine, but right after a PostUpdate i
called for the product that has just been delete

Ex:
CRMProduct.Retreive
expired</description></error></detail
message, WebResponse response, Stream responseStream, Boolea
asyncCall
methodName, Object[] parameters
Any ideas wh
1- PostUpdate is called right after PostDelete
2- Where comes the "new" GUID in OrigObjectXml of the PostUpdate
3- Why does the PostUpdate time out instead of returning "Object no
found" like it does normally when trying to update an object tha
doesn't exist in CRM

Than


Posted by Matt Parks on March 8th, 2005


Have you checked to see if there is another product in the table with the GUID
as it's ID? It possile that there is something going on behind the scense that
is causing it to update another record after the delete. It is common with some
objects in CRM to be unable to access the underlying record on an update due to
locking issues, hence the timeout you are seeing.

Matt Parks
MVP - Microsoft CRM

----------------------------------------
----------------------------------------
On Tue, 08 Mar 2005 02:18:41 -0600, jeanfrancois@kezber-dot-com.no-spam.invalid
(jfmenard) wrote:

I'm creating a post callout object for products in CRM. PostCreate and
PostUpdate work fine, but when I delete a product in CRM, the
PostDelete is called and works fine, but right after a PostUpdate is
called for the product that has just been deleted

Ex:
CRMProduct.Retreive:
expired</description></error></detail>
message, WebResponse response, Stream responseStream, Boolean
asyncCall)
methodName, Object[] parameters)
Any ideas why
1- PostUpdate is called right after PostDelete ?
2- Where comes the "new" GUID in OrigObjectXml of the PostUpdate?
3- Why does the PostUpdate time out instead of returning "Object not
found" like it does normally when trying to update an object that
doesn't exist in CRM?

Thanx



Similar Posts