Ideas object edit page does not respect the "Read-only" and "Required" page layout attributes
Last updated 2022-02-10 ·Reference W-1858923 ·Reported By 9 users
Custom fields that are created for the standard Ideas object, and set to be either "required" or "read-only" on the respective Ideas page layout(s) do not behave correctly on edit. When configured in this fashion, Idea records can be created/edited and saved without values in "required" fields, and fields that should be "read-only" based on the page layout can still be edited.
Based on the help doc below:
the page layout for Ideas was only originally designed to allow for controlling the order of fields. As such, it shouldn't be possible to set fields on Idea page layouts to "required' or "read-only".
1. Login to an org with Ideas enabled
2. Create a two custom fields on the Ideas object, field A and B
3. Once the fields have been created, go to the page layout(s) for the object, and set field A to be "required", and field B to be "read-only".
4. To to create a new Idea record, and notice that you are allowed to edit field B, when it should be "read-only", and that you're allowed to save the record without entering a value into field A.
None available - Idea page layouts are only meant to control field order, not enforce other field properties
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.