How to: Try Out the UI Elements Removal Feature Based on Demonstration Permission Sets
Depending on the setting in the UI Elements Removal field in the Microsoft Dynamics NAV Server Administration tool, only UI elements on objects in the license or on objects that the user has permissions for will appear in the user interface. For more information, see How to: Specify When UI Elements Are Removed.
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. For more information, see How to: Create or Modify Permission Sets.
To try out or demonstrate the effect of the feature to remove UI elements according to user permissions, you can quickly prepare a test UI based on two permission sets (S&R-Customer and S&R-Customer, EDIT) in CRONUS that are ready to support the FOUNDATION permission set for this purpose.
Prepare a permissions-based ORDER PROCESSOR UI that only shows UI elements for creating and editing a customer
Assign the FOUNDATION permission set. For more information, see How to: Define Permissions for Users.
Assign the following two application permission sets, which support the task to create and edit a customer in conjunction with the FOUNDATION permission set:
Upload a user license. For more information, see How to: Upload the License File.
Set the UI Elements Removal field to LicenseFileAndUserPermissions. For more information, see How to: Specify When UI Elements Are Removed.
Start the client for the ORDER PROCESSOR profile.
On the Sales Order Processor Role Center, you now only see the UI elements that are required to create and edit a customer. For example, only the Customers action is visible on the navigation pane, and all the tiles for sales documents are removed from the Activities part. On the involved pages, such as the Customer Card window, you now only see the fields, actions, and page parts that are required to create and edit a customer.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.