CHAPTER 1 - Introduction to X++
CHAPTER 2 - X++ Control Statements
CHAPTER 3 - Objects and Classes
CHAPTER 4: Accessing the Database
CHAPTER 5: Exception Handling
CHAPTER 6: Security for Developers
Lesson 1 – Permissions
The Development I in Microsoft Dynamics AX 2012 training course discussed roles duties and privileges. These security levels cover access to single elements, for example forms, and groups of elements needed to perform a duty. A developer is responsible for defining more granular security levels by setting access on tables and controls in a form, or by associating classes that perform an action with a security permission.
Each form in the Application Object Tree (AOT) has a permissions node that contains either four or five sub-nodes – Read, Update, Create, Delete and Correct. Correct is only displayed if a table in the form has Date Effective data. Under these nodes are four additional nodes – Controls, Tables, Server Methods and Associated Forms.
his topic lists and describes the permission related properties that exist on subnodes under the Permissions node under the node for each form in the AOT. These property values interact with other properties that are set under the AOT > Security node. These values also interact with permission related properties under other high-level nodes such as AOT > Menu Items.
For an example of interaction between security settings, consider a menu item. Suppose you create YourMenuItem at AOT > Menu Items > Display. There you assign values to security properties, such as the ReadPermissions and UpdatePermissions properties. Then you can assign the menu item as a node under AOT > Security > Privilege > ImportantPrivilege > Entry Points. The assignment of the menu item adds the security settings of the menu item to ImportantPrivilege.
On the Entry Point > YourMenuItem node, you can use the AccessLevel property to choose which set of permissions to receive from the menu item into the privilege.