Inactive validation rules
Why is this an issue?
Inactive validation rules add unnecessary clutter to your organization's metadata. As a best practice, validation rules should either be active and serving a purpose, or removed entirely. If a rule needs to be temporarily disabled, make sure to document the reason and set a timeline for review.
Please note, SFDX source format not supported: This rule only analyzes mdapi-format CustomObject files where validation rules are embedded within .object files. It does not detect inactive validation rules in SFDX source format projects where validation rules are stored as individual .validationRule-meta.xml files within each custom object's subdirectory.
Examples
Example of Custom Object's inactive Validation Rule metadata:
<ValidationRule>
<fullName>Account.Require_Phone_Number</fullName>
<active>false</active>
<errorConditionFormula>ISBLANK(Phone)</errorConditionFormula>
<errorMessage>Phone number is required.</errorMessage>
</ValidationRule>
How can I fix violations?
Review why the validation rule was deactivated and decide whether it needs to be reactivated or removed.
When should I disable this rule?
You may dismiss specific violations or disable this rule when inactive validation rules are left intentionally inactive within your org.
Resources