An administrator at Northern Trail Outfitters is building a validation rule on the Opportunity object to enforce data quality standards during stage progression. The rule must trigger an error when an Opportunity is moved to 'Closed Won' with an exceeding if the custom picklist field is left blank. Additionally, to avoid breaking historical records updated via automated background processes, the rule must only enforce this requirement if the record is being edited by a user and either the or field was modified during the current transaction. Which TWO formula conditions must be combined inside the function of the validation rule to meet these requirements correctly?
- ISPICKVAL(StageName, 'Closed Won') && Amount > 100000 && ISBLANK(TEXT(Executive_Sponsor_Approval__c))Cevap
- (ISCHANGED(StageName) || ISCHANGED(Amount))Cevap
- CISBLANK(Executive_Sponsor_Approval__c) && PRIORVALUE(Amount) < 100000
- DStageName = 'Closed Won' && Amount > 100000 && Executive_Sponsor_Approval__c == NULL
- ENOT(ISNEW()) && PRIORVALUE(StageName) == 'Closed Won'
Cevap
The validation rule requires combining two core condition logic blocks: first, converting the picklist value to text to verify if it is blank along with checking the stage and amount threshold; second, utilizing ISCHANGED() on StageName or Amount to ensure historical untouched records do not trigger validation error messages upon background edits.
The correct selection combines two vital formula practices: first, using ISPICKVAL() for stage selection alongside ISBLANK(TEXT()) for evaluating empty picklists; second, wrapping key fields with ISCHANGED() to restrict validation enforcement exclusively to records where the relevant opportunity fields are modified.
Adım Adım Çözüm
Anahtar Kavram
Handling Picklist Null Checks and ISCHANGED Evaluation in Validation Rules
Tahmini Süre:2m 0s