Timeline for How do you make a required field read-only for an object that has a read-only page layout and record type?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2023 at 19:40 | answer | added | sfdcfox♦ | timeline score: 0 | |
| Sep 22, 2023 at 19:22 | comment | added | identigral | You could do the dynamic assignment of perm set if you think the cost of this solution is worth the improved UX, sure. As to the behavior of page layout, feel free to create an enhancement request on Idea Exchange. | |
| Sep 22, 2023 at 19:19 | comment | added | Kevin Judd | I have added a validation rule which prevents the user from changing the value. However, this is a poor UX implementation. The entire state, i.e.., from open to complete of a Work Order can allow a user to edit fields depending on the status. Same user, same permissions, different Work Order status, different field restrictions. Are you suggesting to create permission sets that I toggle based on the status of the Work Order? | |
| Sep 22, 2023 at 19:10 | review | Close votes | |||
| Oct 7, 2023 at 3:04 | |||||
| Sep 22, 2023 at 18:54 | comment | added | identigral | Page layouts are made for all kinds of scenarios. In your particular scenario, it might make sense that (once set) a required field should be read-only. In many other scenarios, it doesn't make sense. You can prevent a user from changing the field via permissions and/or triggers/flows and/or validation rules. trailhead.salesforce.com/content/learn/modules/data_security | |
| Sep 22, 2023 at 18:36 | history | edited | Kevin Judd | CC BY-SA 4.0 |
deleted 1 character in body
|
| S Sep 22, 2023 at 18:35 | review | First questions | |||
| Sep 26, 2023 at 21:06 | |||||
| S Sep 22, 2023 at 18:35 | history | asked | Kevin Judd | CC BY-SA 4.0 |