Skip to main content

NAV 2015 - New Feature UI Element Removal.

HI all,

While Reading Readiness Document for NAV 2015 i came across a commonly asked feature from most of the customer about UI Element Removal. Let's see what document says in the article.

What Microsoft Says -
To simplify the users’ experience in Microsoft Dynamics NAV 2015, we have introduced the UI Elements Removal feature. The feature can be used to remove user interface (UI) elements, such as fields and actions from pages in Microsoft Dynamics NAV so that the Role Center and pages become simpler to look at, easier to navigate on, and faster to get through. 



we will see it in Three Steps.

STEP 1 – Specify When UI Elements Are Removed.

The setup that determines if UI elements are shown according to the license file and/or user permissions.
------------------------------------------------------------------------------------------------------------------------

Now with NAV 2015 we have an option to show user Only Relative Pages and actions which he have permission.

The Setup have two options i.e 
1. Show as per Licensce Permission
2. Show as Per Licensce Permission & user Permission (ROLES)

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.

How to Set IT UP ?

a. Open Microsoft Dynamics NAV Server Administration.
b. Edit the Instance that you want to Change.
c. Set the Value of the UI Elements Removal field.

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. (As Old Days NAV 2009 - NAV 2013 R2)

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 (LicenseFileAndUserPermissionsoption is selected.



-----------------------------------------------------------------------------------------------------------------------

STEP 2- Remove UI Elements Based On Demonstration Permission Sets For a Sample User.
This shows the effect of removing UI elements based on the user’s permissions. It shows for a sample user with a restricted permission set that the resulting Role Center and task pages are simplified.
-----------------------------------------------------------------------------------------------------------------------

a. Open Microsoft Dynamics NAV Windows Client.

b. By Default the Screen Should Show as below -



Now Open User Page and add Permission to a User, Say FOUNDATION.


Add Some More Permissions for the user, 1. S&R-Customer 2. S&R-Customer, EDIT.



Open the Windows Client for the same User and UI Component for which he/she was not have permission are removed.



---------------------------------------------------------------------------------------------------------------------

STEP 3- Remove the Routing No. Field If the User Does Not Have Permission to the Routing Header Table

This demo shows the more advanced use of the UI Elements Removal feature. The demo shows for the Item Card window how the AccessByPermission property can be used to remove UI elements depending on which object(s) the user has permissions to.
----------------------------------------------------------------------------------------------------------------------

For UI elements that are not directly related to an object, you can use the AccessByPermission property to remove an element according to the user’s permission to a related object.

The AccessByPermission property 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 elements 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.

1. In the Microsoft Dynamics NAV Development Environment, view the properties of a table field for which you want to remove its page control(s) or view the properties of a field, action, or part on a page object. For Example Table 27.



2. Select field 99000750, Routing No. and then type Shift+F4 to view the properties.



3. For the AccessByPermission property, choose the AssistEdit button in the Value field.



4. The five different options give flexibility in defining when a UI element is displayed based on users’ permissions.
Object Type - Specify the type of object to which permission is required for the UI element to be visible.
Object ID - Specify the object to which permission is required for the UI element to be visible.
Read - Specify if Read permission is required for the UI element to be visible.
Insert - Specify if Insert permission is required for the UI element to be visible.
Modify - Specify if Modify permission is required for the UI element to be visible.
Delete - Specify if Delete permission is required for the UI element to be visible.
Execute - Specify if Execute permission is required for the UI element to be visible.



All instances of the Routing No. field on pages are now removed if the user does have Insert or Modify permission to the Routing Header table.

IMPORTANT:
If you defined the property for a table field, then all instances of the field on pages are removed from the user’s view. 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.
------------------------------------------------------------------------------------------------------------------------

Hope you find the information useful.

Stay tuned for More about #NAV 2015.

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

Dynamics 365 Business Central 2021 release wave 2 (BC19) Released.

Hi Readers, As we all were expecting Microsoft have Released Business Central 2021 Release Wave 2 Today a.k.a BC19. In this article we will see what all is announced with the General Availability.  Starting Today Customers & Partners can start using Business Central 19. #msdyn365bc #bc19

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.