Use execution context and the form event pipeline
Updated: November 29, 2016
Applies To: Dynamics 365 (online), Dynamics 365 (on-premises), Dynamics CRM 2016, Dynamics CRM Online
Returns the Xrm.Page.context object. See Client-side context (client-side reference) for more information.
Returns a value indicating the order in which this handler is executed.
Returns a reference to the object that the event occurred on.
Retrieves a variable set using 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.
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.
Microsoft Dynamics 365
© 2016 Microsoft. All rights reserved. Copyright