Microsoft KB Archive/939237

= A callout is not fired when you expect it to be fired in Microsoft Dynamics CRM 3.0 =

Article ID: 939237

Article Last Modified on 10/18/2007

-

APPLIES TO


 * Microsoft Dynamics CRM 3.0

-



SYMPTOMS
Consider the following scenarios in Microsoft Dynamics CRM 3.0.

Scenario 1

 * You build a callout.
 * The callout is configured to be fired in the pre-create events or in the post-create events.
 * You expect the callout to be fired when an activity is created by a quick campaign.

Scenario 2

 * You build a callout.
 * The callout is configured to be fired in the pre-assign events or in the post-assign events.
 * You expect the callout to be fired when a user clicks the Accept button to yank a case from a Microsoft Dynamics CRM queue.

Scenario 3

 * You build a callout.
 * The callout is configured to be fired in the pre-create events or in the post-create events.
 * You build a callout that should be fired when you convert a quote to an order. Or, the callout should be fired when you convert an order to an invoice.

Scenario 4

 * You build a callout.
 * The callout is configured to be fired in the pre-create events or in the post-create events.
 * You expect the callout to be fired when a user creates a campaign from an existing campaign or from a campaign template. The user creates the campaign by clicking Copy on the Action menu.

Scenario 5

 * You build a callout.
 * The callout is configured to be fired in the pre-update events or in the post-update events.
 * You expect the callout to be fired when an attachment is modified from an Annotation (Note) entity.

Scenario 6

 * You build a callout.
 * The callout is configured to be fired in the pre-update events or in the post-update events.
 * You expect the callout to be fired when a role entity is modified.

In these scenarios, no callouts are fired.



WORKAROUND
To work around this behavior, you can build a workflow assembly. You can configure the workflow assembly to be fired in these events.

Note This workaround works only in some cases.



STATUS
This behavior is by design.



MORE INFORMATION
In addition to the scenarios that are described in the &quot;Symptoms&quot; section, there are other scenarios in which a callout is not fired when you expect it to be fired. The scenarios that are described in the &quot;Symptoms&quot; section are examples of this behavior.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

933842 The functionality that you expect from a callout .dll file does not work as expected in Microsoft Dynamics CRM 3.0

