Soru

Zorluk: OrtaValidation Rules and Data Quality Enforcement

A Salesforce Administrator is configuring data quality enforcement rules for different business scenarios across standard and custom objects. Match each business requirement with the validation rule formula snippet that correctly implements the required logic.

  • Prevent setting a Lead rating to 'Hot' unless the Annual Revenue field is populated.AND( ISCHANGED( Rating ), ISPICKVAL( Rating, "Hot" ), ISBLANK( AnnualRevenue ) )
  • Prevent modifications to an existing Account Number unless the logged-in user possesses a specific custom permission.AND( NOT( ISNEW() ), ISCHANGED( AccountNumber ), NOT( $Permission.Bypass_Account_Validation ) )
  • Verify that an Account Billing State matches the state corresponding to the entered Billing Postal Code using a Zip Code lookup object.AND( NOT( ISBLANK( BillingPostalCode ) ), VLOOKUP( ObjectType.Zip_Code__c.Fields.State__c, ObjectType.Zip_Code__c.Fields.Name, BillingPostalCode ) <> BillingState )
  • Ensure that a entered Tax ID follows the standard format of three digits, a hyphen, two digits, a hyphen, and four digits.AND( NOT( ISBLANK( Tax_ID__c ) ), NOT( REGEX( Tax_ID__c, "\\d{3}-\\d{2}-\\d{4}" ) ) )

Cevap

Each business requirement correctly maps to its respective formula function: 1 maps to AND with ISCHANGED/ISPICKVAL/ISBLANK; 2 maps to NOT(ISNEW()) combined with $Permission verification; 3 maps to the VLOOKUP function for cross-record validation; 4 maps to the REGEX function for string pattern validation.
Each requirement leverages the appropriate formula function tailored to the target data type and logic requirement: ISPICKVAL and ISBLANK for picklist/null checks, ISNEW and $Permission for record lifecycle and access controls, VLOOKUP for dynamic cross-record lookup comparisons, and REGEX for text pattern validation.

Adım Adım Çözüm

1
Analyze requirement 1 (Rating to 'Hot' requiring Annual Revenue)
Identified the need for ISPICKVAL to evaluate the picklist value, ISCHANGED to detect transitions, and ISBLANK for null checking.
Picklist fields must be evaluated with ISPICKVAL or TEXT in validation rules.
2
Analyze requirement 2 (Account Number edit restrictions)
Matched with NOT(ISNEW()) to exclude newly created records, ISCHANGED for field modification tracking, and $Permission to evaluate custom user permissions.
Validation rules fire on both create and update operations unless constrained by ISNEW().
3
Analyze requirement 3 (Cross-object postal code to state match)
Matched with VLOOKUP, which evaluates field values across custom object data records.
VLOOKUP is specifically designed in Salesforce validation rules to look up values in custom objects based on a key field.
4
Analyze requirement 4 (Tax ID string format enforcement)
Matched with REGEX matching the regular expression string template \d{3}-\d{2}-\d{4}.
Pattern validation for structured text (like SSN, Phone, Tax IDs) requires the REGEX function.

Anahtar Kavram

Salesforce Validation Rule Formula Functions (ISBLANK, ISPICKVAL, VLOOKUP, REGEX, ISNEW)
Bu soruyu puanla