Enabling User Personalization of Forms [AX 2012]
Updated: October 10, 2008
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
Users have several options when they personalize Microsoft Dynamics AX forms. Restrict these options by using the following:
AllowUserSetup property on the form control
AllowAdd property on the form data source field
For more information, see User Personalization of Forms.
For user-personalization to work, the code must be independent from the actual positioning of the control. You must not use any information about the position of the control or assume that the order of the controls is retained.
If the tabChange or tabChanged methods are overridden on a Tab control, users cannot personalize the tabs (for example, by changing their order), regardless of the AllowUserSetup property value.
The parameters received for the FormTabControl.tabChange and FormTabControl.tabChanged methods are based on tabbed page indexes. The parameters are dependent on the current position of the tabbed page. If either method is overridden, prevent users from moving a tabbed page.
Use the following methods instead of the tabChange or tabChanged methods:
These methods operate on the TabPage control. They neither pass information about the current positioning of the tabbed page nor allow full user setup.
Control names need to be unique to help determine which control has been moved.
Controls bound to fields in the Auto field groups are automatically given the following names:
groupName_FieldName for data fields
groupName_M_FieldName for display methods
Avoid using these names elsewhere in the system.
When the user creates new controls, they are automatically given a name that contains the user ID and a counter number.
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. get your copy at the MS Press Store