![\"current](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2021\/03\/1-if-the-logged-in-user-has-ReadWriteUpdate-access-to-any-specific-entity-or-not-1-1.jpeg\")
<\/a>\nSo, when the user is trying to set \u2018Yes\u2019 to the \u2018Create Contact\u2019 field, we want to first check whether the current user has \u2018 to Create\u2019 permission of Contact entity record or not.<\/p>\n
Solution<\/h2>\n
We will achieve this with the help of context.utils.hasEntityPrivilege<\/strong> function that is used to detect whether the current logged-in user has Read\/Write permission for a specific entity or not. In our case, we need to check if the active users have \u2018to Create\u2019 permission for the Contact entity record. Please find the below code that we have used to find out the same. As per the result given by context.utils.hasEntityPrivilege function, we take a decision to create a record contact entity record or not.<\/p>\n Using context.utils.hasEntityPrivilege, we can easily retrieve the current logged in user privilege details.<\/p>\n Introduction In this blog, we will get the idea on how we can check if the current logged-in user has Read\/Write\/Update access to any specific entity or not. Scenario We have one Boolean type PCF control on the Account entity. Based on the Yes \/ No value of PCF control, we want to create a\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"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":[16,19,1929],"tags":[545,592,1941],"class_list":["post-27225","post","type-post","status-publish","format-standard","hentry","category-dynamics-365","category-dynamics-crm","category-pcf","tag-dynamics-365-crm","tag-dynamics-crm","tag-pcf-control"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/27225","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=27225"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/27225\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=27225"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=27225"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=27225"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\ncontext.utils.hasEntityPrivilege(“contact”,1,3)
\nwhere,
\ncontact = Entity type name for which we have to find privilege details for the said entity.
\n1 = It indicates Entity privilege type such as Read, Write, etc. In the above scenario, we check for Create privilege so 1 is associated with \u2018Create\u2019. Please find some other Entity type names with their code:
\nNone = 0
\nCreate = 1
\nRead = 2
\nWrite = 3
\nDelete = 4
\nAssign =5
\nShare =6
\nAppend =7
\nAppendTo =8
\n3 = It indicates the entity privilege depth of the specified entity. It has the following values:
\nNone = -1
\nBasic = 0
\nLocal = 1
\nDeep = 2
\nGlobal = 3
\nSo, by calling this function, we found that the current logged in user has \u2018to Create\u2019 permission for Contact entity record as shown in the below screenshot:<\/p>\n<\/a><\/p>\nConclusion<\/h2>\n
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"