{"id":23873,"date":"2020-06-16T13:48:34","date_gmt":"2020-06-16T13:48:34","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=23873"},"modified":"2021-08-25T11:15:38","modified_gmt":"2021-08-25T11:15:38","slug":"how-to-get-users-security-role-name-using-client-api-in-dynamics-365-crm","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/06\/how-to-get-users-security-role-name-using-client-api-in-dynamics-365-crm\/","title":{"rendered":"How to get user\u2019s security role name using client API in Dynamics 365 CRM"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

While doing any development with Dynamics 365 CRM, there might be a requirement of handling a few things like form attributes based on the security role. In many projects or applications of Dynamics 365 CRM where developers have to handle a few fields or tabs of CRM by showing\/hiding the same to Dynamics 365 users based on their security role. To do so, developer retrieves the security role of logged-in user and checks for the specific security role to show\/hide fields or any other controls of CRM.<\/p>\n

Now, to retrieve the user\u2019s security role we were using Microsoft client API as below:<\/p>\n

var userSettings = Xrm.Utility.getGlobalContext().userSettings<\/strong><\/p>\n

Using above API we get the logged-in user\u2019s details like User Id, Date format, Security roles, etc.<\/p>\n

Further, to get the security roles we used userSettings.securityRoles<\/strong><\/p>\n

So, using this we get the list of all role Id of security roles assigned to the logged-in user. However, we could not get the security role names. So, we need to write another code to retrieve all the security roles from CRM and then, we need to write the logic to get the security role name by using the role Id.<\/p>\n

However, now we do not have to write extra code to get security role name based on the role Id which was assigned to user. In the spring release of 2020, Microsoft has provided alternate API to the deprecation of userSettings.securityRoles<\/strong>. Microsoft has replaced this API with \u00a0Xrm.Utility.getGlobalContext().userSettings.roles<\/strong>.<\/p>\n

So, using the updated API we get\u00a0 logged-in user\u2019s security roles with its role Id in the _collection as shown in the screenshot below:<\/p>\n

\"client<\/p>\n

Now, it became easier for developers to get the current user\u2019s security role name and achieve the functionality like show\/hide or enable\/disable any form attributes programmatically as per requirement. It will save time and line of code of developer as we will get the desired result i.e. role names with this updated Client API.<\/p>\n

Conclusion<\/strong><\/p>\n

Using the updated client API, we will get the user\u2019s security role name easily without writing any extra code.<\/p>\n

Free 70% of storage space in CRM with Attachment Management Apps!<\/div><\/div><\/h2>\n

Attach2Dynamics<\/a> – Store and manage documents\/attachments in cloud storage of your choice – SharePoint, Dropbox or Azure Blob Storage from within Dynamics 365 CRM.<\/em>
\nSharePoint Security Sync<\/a><\/strong> \u2013 Robust and secure solution to integrate Dynamics 365 CRM and SharePoint Security Sync thereby ensuring secure access to confidential documents stored in SharePoint.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction While doing any development with Dynamics 365 CRM, there might be a requirement of handling a few things like form attributes based on the security role. In many projects or applications of Dynamics 365 CRM where developers have to handle a few fields or tabs of CRM by showing\/hiding the same to Dynamics 365\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":23876,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1],"tags":[2046],"class_list":["post-23873","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-client-api-in-dynamics-365-crm"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/23873","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=23873"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/23873\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/23876"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=23873"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=23873"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=23873"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}