Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
User actions on a form are input through mouse pointers and keyboards. These actions cause events that are recognized by Microsoft Dynamics AX. The recognized events include the following:
The system reacts to each event by executing several event methods. The user is often unaware that these methods are being executed.
- Event Method Sequences when the Value of a Control Changes
- Event Method Sequences when a Form is Closed
- Event Method Sequences when a Form is Opened
- Event Method Sequences when a Record is Created
- Event Method Sequences when a Record is Deleted
- Event Method Sequences when Focus is Removed from a Record
Use the Application Object Tree (AOT) to override the event methods and customize the response to form events.
- Expand the Forms node to see its Methods subnode.
- Expand the Methods node to see a subnode for each method that is currently overridden.
- Right-click the Methods node, and then select Override Method to see a list of methods that have not yet been overridden.
- Expand other nodes under Forms to see additional Methods nodes.
Information about the sequence of event method execution is useful when you are determining the correct method to override. For example, you could write code to log the inserts that the user causes when they enter data into a grid control. This code could be placed in various event methods. You could override the insert event method on an underlying table. By knowing the aosValidateInsert method is executed immediately after the insert method, you might instead choose to log the aosValidateInsert method. OverridingaosValidateInsert might provide log information that has the results of security checks.
Aucun commentaire:
Enregistrer un commentaire