Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 939237 - Last Review: October 18, 2007 - Revision: 2.0
A callout is not fired when you expect it to be fired in Microsoft Dynamics CRM 3.0
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.
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.
This behavior is by design.
In addition to the scenarios that are described in the "Symptoms" 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 "Symptoms" section are examples of this behavior.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
933842Â
(http://kbalertz.com/Feedback.aspx?kbNumber=933842/
)
The functionality that you expect from a callout .dll file does not work as expected in Microsoft Dynamics CRM 3.0
For more information about how to build a callout in Microsoft Dynamics CRM, or about how to configure a callout, see the software development kit (SDK) document. To download Microsoft Dynamics CRM 3.0 SDK version 3.0.7, visit the following Web site:
APPLIES TO
- Microsoft Dynamics CRM 3.0
| kbmbscustomization kbexpertisebeginner kbtshoot kbmbsmigrate kbexpertiseinter KB939237 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate