Difference between making field required in page layout vs while field creation.
I am wondering what is the difference between making a field required on the page layout v/s checking the required chechbox during field creation?
If you leave that unchecked and make it required on only one page layout, then that's the only method of data entry for which a value is required in that field.
I hope that helps!
if a field is required in the page layout and read only in the field-level security settings, the field-level security overrides the page layout and the field will be read only for the user
To automatically add a field to all page layouts and make it visible and required everywhere regardless of field-level security, make it a universally required field.
Required while creating : Cannot be bypassed by any way (API/Dataloader/Imports)
Requied on Page Layout : Required only when one works on the UI (inline editting/creating record on page/edit record on page)
Can you let us know, in what context are you asking this, if you have a requirement/ example ?
This validation for "Required" field is checked whenever you are trying to save a record (created/ edited ).
If the field has been made "Required" only at Page Layout level, in that case, it will be required only when one works on the UI on that particular page ( create/edit record on page).
To be checked everytime when saving a record for that object ( via any other ways API, imports, related objects etc..) you need to set the field as Required at field level.