cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
bs-dev001
Advocate I
Advocate I

Allow users to edit a certain field on Contact table

I want a certain group of users to be view-only on Contact table but allow those users to edit a certain field on Contact table.

What is the best way to achieve that?

1 ACCEPTED SOLUTION

Accepted Solutions
dpoggemann
Super User
Super User

Hi @bs-dev001 ,

 

The only way "out-of-the-box" to do this is to utilize Field level security if you want to control at the field level within the table.  Check out this good video walking through the functionality:   https://youtu.be/S6SZu8uhKOo 

 

Now, from a pragmatic perspective this can be a bit of a pain since you are basically going to have to enable all fields on the entity for field level security and then open up a few of the fields on the Entity for this group to modify and lock down all other fields...

 

Another option here is to actually setup another table for this that is related to the Contact in a (N:1) relationship and have this table the couple / few fields the users would modify.  You could then give them read only access to the contact and setup the security for them to update the fields on this table.  You would not allow create on the table by anyone and just create it automatically (based on workflow) run by admin user when the Contact is created... 

 

Just another thought 😉

 

Hope this helps.  Please accept if answers your question or Like if helps in any way.

 

Thanks,

Drew

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

View solution in original post

1 REPLY 1
dpoggemann
Super User
Super User

Hi @bs-dev001 ,

 

The only way "out-of-the-box" to do this is to utilize Field level security if you want to control at the field level within the table.  Check out this good video walking through the functionality:   https://youtu.be/S6SZu8uhKOo 

 

Now, from a pragmatic perspective this can be a bit of a pain since you are basically going to have to enable all fields on the entity for field level security and then open up a few of the fields on the Entity for this group to modify and lock down all other fields...

 

Another option here is to actually setup another table for this that is related to the Contact in a (N:1) relationship and have this table the couple / few fields the users would modify.  You could then give them read only access to the contact and setup the security for them to update the fields on this table.  You would not allow create on the table by anyone and just create it automatically (based on workflow) run by admin user when the Contact is created... 

 

Just another thought 😉

 

Hope this helps.  Please accept if answers your question or Like if helps in any way.

 

Thanks,

Drew

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

Helpful resources

Announcements
Power Platform Call June 2022 768x460.png

Power Platform Community Call

Join us for the next call on August 17, 2022 at 8am PDT.

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Users online (1,608)