![]() Delete permission includes every other permission. Read is the weakest permission, and Delete is the strongest. The permission values for the EffectiveAccess property represent a hierarchy. The descriptions of the properties for the Read node apply to Update, Create, and Delete nodes. This section describes the properties for the AOT node at Forms > YourForm > Permissions > Read > Controls > YourControl. NeededPermission property on control ControlName is set to none. When you compile the form an error message similar to the following is generated: In this scenario the node representing the control is not automatically removed from the permission group. Later you set the NeededPermission property of the control to None. Suppose a control was manually added to a permission group. You can set the NeededPermission value to None to enable access to the control without any restrictions. When you specify Manual for the NeededPermission property, the automatic inference system does not add a node representing the control as a subnode under the permission group nodes in the AOT. You can insert the control subnode manually under the permission group nodes. The following table describes the special values that can be assigned to the NeededPermission property of a control. ![]() This occurs when you specify a value for the NeededPermission property of the control. Through automatic inference the system inserts a subnode representing the control, under the appropriate permission group nodes in the AOT. But the control is visible to another user who has Update or Delete permission to the control. A user who has only Read permission does not see the control on the form. For example, suppose a control has its NeededPermission property set to Update. To see a particular control on a form, the user must have a permission to the control that is at least as strong as the permission the control requires. Therefore Read is also included by Create permission. Read is included by Update, and Update is included by Create. The values for the NeededPermission property represent a hierarchy. This section describes the NeededPermission property for the AOT node at Forms > YourForm > Designs > Design > YourControl. The Read and Delete nodes can be referred to as permission group nodes.Īll of the permission group nodes contains the same subnodes that are shown under the Read node. The nodes at the level of Read through Delete contain many individual permissions. The following list shows the position of the Permissions node under the Forms node in the AOT: Permission Group Nodes under Forms in the AOT 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. The assignment of the menu item adds the security settings of the menu item to ImportantPrivilege. Then you can assign the menu item as a node under AOT > Security > Privilege > ImportantPrivilege > Entry Points. There you assign values to security properties, such as the ReadPermissions and UpdatePermissions properties. Suppose you create YourMenuItem at AOT > Menu Items > Display. These values also interact with permission related properties under other high-level nodes such as AOT > Menu Items.įor an example of interaction between security settings, consider a menu item. These property values interact with other properties that are set under the AOT > Security node. This 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. Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |