Skip to main content

#Validation Rules5 discussing

Getting a generic: "Whoops, looks like there was a problem. Please try again." 

error on Create Validation Rules challenge. I am 99.99% sure I have correctly completed the challenge. I have refreshed, cleared cache, tried in another browser, but still getting that error.  

 

#Trailhead Challenges  #Trailhead  #Validation Rules

2 answers
  1. Aug 12, 5:31 AM

    Hello @Elan Wong 

    You can try the following options:

0/9000

Lock In Your Account Data Model

 Validation rules to keep data clean in the NPSP

household account model. And four easy steps can help keep those validation rules working while also using lead conversion.  

 

Lock In Your Account Data Model Validation rules to keep data clean in the NPSP household account model.

 

 

 

@Admin Group, Philadelphia, US @Nonprofit User Group, Philadelphia, US @Admin Group, West Chester, US @Nonprofit and Education MindShare

  

 

#NPSP  #Validation Rules

3 comments
  1. Jul 24, 7:54 PM

    Very true and good point.  Sigh, sometimes I wish SF would make these kind of features work instead of AI. 

0/9000
5 answers
  1. Nov 22, 2025, 9:58 PM

     It sounds like the validation rule is saved but not being recognized during the check. Make sure the rule is active, the error condition formula is correct, and that the challenge test data actually triggers the rule. Sometimes Trailhead requires very specific field names or conditions to match their criteria. If everything looks right, try refreshing the playground or creating a new one, as playground glitches can prevent the checks from running properly. This usually resolves the issue. 

0/9000
1 comment
  1. Jul 21, 2025, 7:07 PM

    Hi @abirami panneerselvam, Thank you for reaching out to the Trailblazer Community. We assume this issue needs further review and we may need access to your playground. We will reach out to you via email to investigate further.

     

    ++CreateTrailheadCase

     

    You can ignore the command above, it is a tool used by our Agents to tell the system to create your case.

     

    Thank you!

0/9000

Hello,  

 

I have a validation rule written as such:  

 

AND( 

OR( 

ISPICKVAL(StageName, "Budget"), 

ISPICKVAL(StageName, "Sales Quote"), 

ISPICKVAL(StageName, "Negotiation / Review") 

), 

 

ISCHANGED( CloseDate ), 

$

Profile.Name

 <> "System Administrator", 

$User.Username <> "

yaritza.romo@hollman.com

 

 

It is currently saying (with additional parameters) opportunity close date cannot be changed at all - how can i revise this to say that a close date CAN be brought in from another month, but NOT pushed out from this month? 

 

(we are trying to keep our pipeline honest - need rules to help, not allowing sales users to push out opps but definitely bring in opps if they can)  

 

PUSH OUT = Edit close date to be in a future month 

BRING IN = Edit close date to be in current month 

 

Thanks! 

 

@Admin Group, Dallas, US #Validation Rules

 

@Who owes me a beer?!?

10 comments
0/9000

I have created one Custom validation rule on Lead status field that will check if the Lead.IsConverted is true and the previous value of Status is not "Contacted" then It will display error. 

I want this because on the contacted status first I am killing all the time-based workflows and then I want to convert the lead so that the "Unable to convert lead that is in use by workflow" will not occur. But this won't happen, the "Unable to convert lead that is in use by workflow" will display if the time-based workflows are there and I am trying to change status from "Open" to "Converted".

 

Here I want to display my custom validation error before "Unable to convert lead that is in use by workflow" error.Is there any way we can do this? I also tried with Before Saved record trigger flow but that also not worked.

Is there any other work around we can achieve this?

0/9000

Any ideas?

 

Validation in salesforce passes syntax but doesn't work

 

AND(ISNEW(), CONTAINS( Subject , "Employee Huddle") || CONTAINS( Subject ,"Inside Track") || CONTAINS( Subject ,"IT Maintenance") || CONTAINS( Subject ,"Carrier Updates & Commercial Corner"), CONTAINS( Subject ,"IT Important") || CONTAINS( Subject ,"EPIC Maintenance") || CONTAINS( Subject ,"EPIC Downtime") || CONTAINS( Subject ,"IT Alert") && ISPICKVAL ( Type, "Insurance") && ISPICKVAL ( Origin, "Email")).

 

#Validation Rules

7 comments
0/9000

I need to enforce the picklist when creating an event so that manual text input is not possible. I think I need to use the ISPICKVAL function but am not sure what to put as the "picklist_field, text_literal" part.

 

#Validation Rules

3 answers
  1. Oct 23, 2024, 8:32 PM

    @Kate Williams are you just trying to make the field itself required?  or validate specific values selected?

     

    If you just want to make the Picklist required you can use an ISBLANK and TEXT Function like this

    ISBLANK(TEXT( Field_Name ))
0/9000
3 answers
  1. Oct 23, 2024, 8:30 PM

    Are the fields DateTime or just Time?  

     

    If they are just Time field could you ever have a scenario where the Departure could be 10:00 PM and the Arrival 6:00 AM the next day?  Or are they always within the same day?

0/9000

On a date/time field, I want to put in a validation rule for user to only put top of the hour. This means they can't put 1:15pm, 1:30PM, 1:45pm. They can only do 2pm,3pm,4pm, etc. 

 

#Data Management  #Validation Rules  #Salesforce Developer

4 answers
  1. Oct 16, 2024, 3:07 PM

    Please try below formula, worked for me.

    MOD( VALUE( MID( TEXT( DateTime_Field ), 15, 2 ) ), 60 ) <> 0

0/9000