Salesforce Fact #849 | Making field read only using dynamic forms and custom permission access

Another use case of dynamic forms. Suppose, we want to make a field read only for all users and would like to make it editable only if the user is assigned a particular custom permission.

We can make use of dynamic forms and take two instances of that field along with the filter conditions accordingly. In this example, we have made the LeadSource field on Opportunity read only for most users and editable only if the user is assigned the 'Test_Custom_Permission'.

Note: Admin users will always see the field as editable because of the system permission 'edit read only fields'. Dynamic forms are not supported for community.

Attached are the screenshots.




Comments

  1. Steven SmithJune 14, 2024 at 6:10 PM

    Whether you're looking to Do my assignment or develop innovative solutions to complex problems, understanding AI and its implications is key to thriving in the future.


    ReplyDelete
  2. 360 Degree CloudJune 17, 2024 at 11:19 AM

    best

    ReplyDelete

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more