T
Tuomas
Hi,
We have a .NET web service that creates CRM order programmatically.
There is a post-callout configured to the order create and update
events. This callout is triggered and works fine when a new order is
created from CRM web UI or an existing order is updated from the CRM
web UI. But when a new order is created by our web service, the
callout component is not triggered at all even though the order is
created fine. The CRM user account that we use to make the SDK call to
create a new order belongs to CRM admin role. The code that creates
the new order uses the Execute method and passes the
CompoundCreateRequest object as parameter. Does that make any
difference if an Execute method is used instead of the Create method?
Is there some type of special configuration needed for the callout
component when it should be triggered from code?
Any suggestions are greatly appreciated.
Thanks.
We have a .NET web service that creates CRM order programmatically.
There is a post-callout configured to the order create and update
events. This callout is triggered and works fine when a new order is
created from CRM web UI or an existing order is updated from the CRM
web UI. But when a new order is created by our web service, the
callout component is not triggered at all even though the order is
created fine. The CRM user account that we use to make the SDK call to
create a new order belongs to CRM admin role. The code that creates
the new order uses the Execute method and passes the
CompoundCreateRequest object as parameter. Does that make any
difference if an Execute method is used instead of the Create method?
Is there some type of special configuration needed for the callout
component when it should be triggered from code?
Any suggestions are greatly appreciated.
Thanks.