How to add condition in Field Level Security in Dynamics 365 (Onpremise)

(0) Share

Report

Posted on by Community Member

Hi All,

I have a scenario like Contact entity have few sensitive data which should not be visible to different BU users, e.g:- If X user create contact which has sensitive info on few fields and he's belongs to AA business unit, now Y user open the same contact record and he's belongs to BB business unit, the sensitive info. fields should not be visible to Y user as he's from different business unit. Fields should be masked like *******

In OOB FLS I tried to restrict but can't achieve. Also I had tried in JS by comparing Owenr's BU and Logged on user's BU to hide/show the sensitive data but still this would be visible in Advanced Find and other places.

Please help how to achieve this using plugin/custom workflow.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Verified answer

Alex Fun Wei Jie 33,628 on at

Like (1)

Report
Copy link

Link copied!

Hi,

In your scenario , you might need to build a plugin to achieve that. You can take a look into a feature called shared secured field.

First , What is Shared secured field

[View:https://myencounterwithcrm.wordpress.com/2014/12/03/crmshared-secured-field/:750:50]

How do we share the secured field through plugin or custom workflow

[View:https://community.dynamics.com/crm/b/zhongchenzhoustipstricksandportaldevelopment/archive/2012/06/27/dynamics-crm-2011-share-secured-fields:750:50]

[View:https://community.dynamics.com/crm/b/zhongchenzhoustipstricksandportaldevelopment/archive/2012/06/27/dynamics-crm-2011-share-secured-fields:750:50]

You also can join this group and follow the post below on how to manipulate the shared secured field through plugin code, the scneario is different,but there are some steps you can follow.

https://www.facebook.com/groups/108321812579187/permalink/1292577790820244/

Was this reply helpful? Yes No
Suggested answer

RaviKashyap 55,410 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi Sathesh,

You could still use the OOB FLS but you need to manage the users manually i.e. if you create the security profile, you need to add the users manually.

Or you can create a team and then add the users in that team.

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report
Copy link

Link copied!

Another option might be to move those fields to a new entity and to configure the security roles so that users can only see sensitive information in their business units (Then have a lookup from the contact to that entity.. and, maybe, add that entity's quick view form to the contact form)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks Wei, this Blog helps, via custom workflow I able to control sharing privileges of Read, Update based on my business scenario. Thanks

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

No I can't achieve this by OOB.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Yes I suggested the same but my client didn't like this as they have similar scenario in another custom entity which has only 2 sensitive fields, so creating entity for 2 fields is not fair.

Was this reply helpful? Yes No
Alex Fun Wei Jie 33,628 on at

Like (0)

Report
Copy link

Link copied!

Hi

glad this help. Remember to close the thread if this solved your problem

Was this reply helpful? Yes No