You can configure Microsoft Dynamics NAV to show and hide user interface (UI) elements based on the license or the user's permissions to the underlying tables. All elements, fields, actions, and page parts, can be removed from the user’s view of Microsoft Dynamics NAV.
Depending on the setting in the UI Elements Removal field in the Microsoft Dynamics NAV Netţjónsstjórnunartól, only UI elements on objects in the license or on objects that the user has permissions to will appear in the user interface.
UI elements that are directly related to an object through the TableRelation or the CalcFormula property can be removed automatically according to the license file and/or user permissions.
For UI elements that are not directly related to an object, you can use the AccessByPermission property to remove the element according to the user’s permission to a related object.
To make full use of the LicenseFileAndUserPermissions option in the UI Elements Removal field, it is recommended that you assign the special permission set, FOUNDATION, along with the relevant permission sets that define which application objects the user will access.
 Mikilvćgt |
|---|
| The majority of the permission sets that are provided with the CRONUS demonstration database cannot be combined with the FOUNDATION permission set to fully use the UI Elements Removal feature. You must first create or edit the relevant permission sets to avoid that the user is blocked from performing the involved tasks. You must first create or edit the relevant permission sets to avoid that the user is blocked from performing the involved tasks. If you only use the LicenseFile option in the UI Elements Removal field, then you do not have to edit any permission sets as they will not affect which UI elements are removed. |
A couple of permission sets in the CRONUS demonstration database are adapted to support the FOUNDATION permission set for demonstration purposes. You can use those permission sets to try out how UI elements are removed for a user performing the task to create and edit a new customer.
The following table describes a sequence of tasks, with links to the topics that describe them. These tasks are listed in the order in which they are generally performed.
| To | See |
|---|---|
Configure Microsoft Dynamics NAV Netţjónn to automatically remove UI elements from the user’s interface if they are on objects that are not in the license or on objects that the user does not have permissions for. | |
Use the AccessByPermission property to define which user permissions to a certain object are required before the user can see and access the UI element. This method can be used to remove UI elements without a direct object relation from the user’s interface based on permissions. | How to: Remove UI Elements Using the AccessByPermission Property |
To experience how UI elements are removed for a user performing the task to create and edit a new customer, create a sample user interface based on two permission sets that are provided with Microsoft Dynamics NAV. | How to: Sample the UI Removal Feature Based on Default Permission Sets |
Learn about FOUNDATION and other special permission sets. | |
Modify the existing permission sets to fully support the FOUNDATION permission set. |