Export (0) Print
Expand All

Use Execution Context and the Form Event Pipeline

[Applies to: Microsoft Dynamics CRM 2011]

This topic describes how to use the Form event pipeline to manage multiple event handlers for an event, and how to use execution context to re-use JScript library functions for different events.

Execution Context

When you associate a function in a JScript library to an event handler in Microsoft Dynamics CRM, you can check the Pass execution context as first parameter option. The following table lists the execution context object methods.

 

Method Description

getContext

Returns the Xrm.Page.context object.

getDepth

Returns a value indicating the order in which this handler is executed.

getEventSource

Returns a reference to the object that the event occurred on.

getSharedVariable

Retrieves a variable set using setSharedVariable.

setSharedVariable

Sets the value of a variable that can be used by a hander after the current handler finishes.

Use the getEventSource method in functions to make them more generic. For example, if you have a function that formats a telephone number, you can use the getEventSource method to refer to whatever attribute caused the onChange event. Your functions do not need to reference a specific attribute.

Form Event Pipeline

You can define up to 50 handlers for each event. Each handler is executed in the order that it is displayed on the Events tab of the form element properties dialog box. This corresponds to the list of <Handler> (FormXml) elements in the <Handlers> (FormXml) element for an event.

Use the setSharedVariable and getSharedVariable methods to pass a common variable between functions. Use the execution context getDepth method to know the sequence that a function is being executed in relative to other handlers.

See Also

Microsoft Dynamics CRM 2011
Send comments about this topic to Microsoft.
© 2013 Microsoft Corporation. All rights reserved.

Community Additions

ADD
Show:
© 2015 Microsoft