We all know that Field-Level security (FLS) and Page Layout are very important concept. But let us understand the concept with multiple use cases. I always believe going through use cases/scenarios are the best way to learn the concept.Use Case 1:Object Name: StudentField Name: Student NameField is required: YesLet’s try to change the field’s security both in profile level as well as through page layout.Changing though Field Level Security @ Profile Level (say for profile: Sales User) –You can’t change Field Level Security for a field if the field is marked as required during declaration. The field will become visible for all the profiles as shown below -So is it possible to do something in page layout? Let’s check –Seems like here also you can’t do any changes. Below is the screenshot –So the conclusion is that if a field is marked as required during declaration, that field will remain required and visible in all the page layouts. You can’t make that field read-only also.Use Case 2:Object Name: StudentField Name: Student AgeField is required: NoNow we can have multiple scenarios. They are listed below –Scenario 1:Visible for Profile – Sales User: NoVisible for Profile – Executive User: YesRequired in Page Layout – YesObservation:Logged in as Adams, Karen (Profile – Sales User)Logged in as Bassi, Brent (Profile – Executive User)Scenario 2:Visible for Profile – Sales User: YesRead Only for Profile...Read More
Category: field-level security
- Salesforce API – New and Changed Objects
- New Video – Mastering Google Cloud Storage Part 3 – Diving Deep into Retention Policies!
- Salesforce Winter 24 Release | Sharing Related Enhancements
- How To Perform Enhanced List Sorting with Comparator Interface
- Unleashing The Power of AI: Salesforce and Tableau GPT