Sets a value for a table field or UI element that determines the permission mask for an object that a user must have to see and access the related page fields or UI element in the client. The UI element will be removed at runtime if the user does not have permissions to a certain object as specified in the Access by Permission window.
Depending on the setting in the UI Elements Removal field in the Microsoft Dynamics NAV Server Administration tool, only user interface (UI) elements on objects in the license or on objects that the user has permissions to will appear in the user interface.
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.
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.
To specify when UI elements are removed
- Open the Microsoft Dynamics NAV Server Administration
- In the UI Elements Removal field, choose the relevant option as described in the following table.
| Option | Description |
| None | All UI elements are displayed, even if the license file does not include the related object and the user does not have permissions to the related object. |
| LicenseFile | A UI element is removed if the related object is not included in the license file. |
| LicenseFileAndUserPermissions | A UI element is removed if the related object is not included in the license file and the user does not have permissions to the object as defined in the AccessByPermission property for the related UI element.
By default, this option is selected. |
When you configure user interfaces in Microsoft Dynamics NAV, you should make sure that the UI Elements Removal field is set to its default, LicenseFileAndUserPermissions, so that you only see the relevant UI elements in the Customize window.
When you develop in Microsoft Dynamics NAV, you should make sure that the UI Elements Removal field is set to its default, None, to make sure that all UI elements are visible when you review your development in the UI.
All types of UI elements will be removed if they relate to objects that are not included in the license or the user does not have the required permission to the objects:
- Fields
- Actions
- Page parts
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
All types of UI elements will be removed if they relate to an object to which the user does not have the required permissions:
Fields on pages, including FactBoxes
Actions on pages, including toolbars and navigation panes
Page parts, such as Lines FastTabs
Note
To use this property, the UI Elements Removal field in the Microsoft Dynamics NAV Server Administration tool must be set to LicenseFile or LicenseFileAndUserPermissions.
This Property Applies To
Fields in tables (affecting all related fields on pages)
Fields on pages
Actions on pages
MenuSuite items
Page parts, such as a Lines FastTab
Property Value
When you choose the AssistEdit button, the Access By Permission window opens. Fill the fields as described in the following table.
| Field | Description |
| Object Type | Specify the type of object to which permission is required to display the UI element. |
| Object ID | Specify the object to which permission is required to display the UI element. |
| Read | Specify if Read permission is required to display the UI element. |
| or Insert | Specify if Insert permission is required to display the UI element. |
| or Modify | Specify if Modify permission is required to display the UI element. |
| or Delete | Specify if Delete permission is required to display the UI element. |
| or Execute | Specify if Execute permission is required to display the UI element. |
Note
If multiple permissions are selected, then one or the other applies.
Example: Remove the Unit Price field if the user does not have permission to the Sales Price table
Open table 27, Item Card, with the Table Designer.
View the properties of field 18, Unit Price.
For the AccessByPermission property, choose the AssistEdit button in the Value field.
In the Access By Permission window, fill the fields as described in the following table.
| Field | Description |
| Object Type | TableData |
| Object ID | Sales Price |
| Read | Select |
| Insert | Select |
| Modify | Leave blank |
| Delete | Leave blank |
| Execute | Leave blank |
Close the Access By Permission window and save the changes on table 27.
All instances of the Unit Price field on pages are now removed if the user does have Read or Insert permission to the Sales Price table.
Important
If you defined the property for a table field, then all instances of the field on pages are removed. To override the property on an individual page field, delete the permission value after the = sign in the Value field. Do NOT delete the whole string as that will be replicated on the property of the table field.
Note
To use the LicenseFileAndUserPermissions option in the UI Elements Removal field, you must assign the special FOUNDATION permission set to the user along with the relevant application permission sets that define which application objects the user will access. Unlike the BASIC permission set, the FOUNDATION permission set only grants access to application setup and system tables and requires that other assigned permission sets define which specific application objects can be accessed.
Not all of the 167 default permission sets that are provided with Microsoft Dynamics NAV are ready to support the FOUNDATION permission set to remove UI elements according to user permissions. You must therefore edit the relevant permission sets as explained in the following procedures.
To experience how UI elements are removed for a user performing the task to create and edit a new customer, you can create a sample user interface based on default permission sets provided with Microsoft Dynamics NAV.
Special Permission Sets
The following permission sets have special definitions that you should be aware of as you implement permissions and security for Microsoft Dynamics NAV users.
| Permission set | Definition |
| SUPER | Can read, use, update, and delete all data and all application objects in the scope of your license. Microsoft Dynamics NAV requires that at least one user be assigned this permission set in each database.
You cannot modify permissions for the SUPER permission set. |
| SUPER (DATA) | Can read, use, update, and delete all data. You typically assign this permission set to an accounting manager who needs to work with all data but does not need to change Microsoft Dynamics NAV.
This permission set does not give access to the Object Designer. |
| SECURITY | Can create new users and assign them the same permission sets. Must be able to access the User, User Property, Permission Set, and Access Control tables.
For example, you can create a SECURITY permission set that includes the four required tables and any additional permissions that you want to include. You can then assign this permission set to a user who is a department administrator. This user can then administer permissions for other users in their department. Only a user who has the SUPER permission set can create and modify a SECURITY permission set. Users who have this permission set can assign the same permissions to other users, but they cannot assign themselves the SUPER permission set. |
| BASIC | Grants Read access to almost all application tables and all system tables.
The main purpose of this permission set is to enable the client to open and show all pages. When you create a new database, you must import the BASIC permission set from an XML file. |
| FOUNDATION | A prerequisite for all other permission sets. The FOUNDATION permission set grants access to system tables and application setup tables that are required for most application features to work.
Note This permission set is recommended when using the UI Elements Removal feature to automatically remove UI elements according to user permissions. |
ARKSD Consultancy Private Limited 