First question on Salesfoce :-)
It says here (bold is what concerns me):
Triggers and Order of Execution
On the server, Salesforce:
- Loads the original record from the database or initializes the record for an upsert statement.
- Loads the new record field values from the request and overwrites the old values. If the request came from a standard UI edit page, Salesforce runs system validation to check the record for:
- Compliance with layout-specific rules
- Required values at the layout level and field-definition level
- Valid field formats
- Maximum field length
Salesforce doesn't perform system validation in this step when the request comes from other sources, such as an Apex application or a SOAP API call.
- Executes all before triggers.
- Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any user-defined validation rules. The only system validation that Salesforce doesn't run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
- Saves the record to the database, but doesn't commit yet.
My question is:
Are layout-specific rules the same thing as Validation Rules? If nto, what's the difference?
Thanks,
Florent
Ps: big, BIG, HUUUGE up for all those that answer Salesforce questions. It is indeed so very useful!
10 answers
layout-specific rules are different from Validation Rules. layout specific rules are system validation rules that include things like:
- Required values at the layout level and field-definition level
While validation rules can be custom validation rules.
