• Ashish_Tiwari
  • NEWBIE
  • 19 Points
  • Member since 2016
  • Business Analyst


  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
    Questions
  • 3
    Replies

Formulas & Validations
Creating Validation Rules

I'm running into problems with the check not working. I've read through over a dozen forum posts prior to creating this one.

I followed this video exactly: https://www.youtube.com/watch?v=PUByNV8NAPY

I've tried every example code contained in every single post. I've been trying this "15 min" module for 3 hours.

Here is my error every single time: 

Challenge Not yet complete... here's what's wrong: 
The validation rule failed to enforce the business logic

User-added image
User-added image
Please let me know any advice or solutions. This is extremely frustrating. Thanks.

I have done everything but I still get this error that is not helpful becauseI have done what it asks.

Challenge Not yet complete... here's what's wrong:
Either the contact object does not have a compact layout named 'Phone and Email', or it is not set as the primary compact layout
  1. I created a custom object 'Contact'
  2. I created custom fields of name (text), phone (phone type), mobile (phone type), and email (text type).
  3. Then I made a new custom compact layout called 'Phone and Email'
  4. I make 'Phone and Email' my primary compact layout
What did I do wrong?? Am I missing a step?? Please help.
Hello,

I created the validation rule and checked that it worked in my org.
When I check it through trailhead, I get this error:
Challenge not yet complete... here's what's wrong: 
There was an unexpected error in your org which is preventing this assessment check from completing: System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Zip Code does not match Account Shipping Zip Code: []

A different thread suggested deactivating the rule but when I do so I get this:
Challenge not yet complete... here's what's wrong: 
The validation rule failed to enforce the business logic


For reference, this is the validation rule.
(NOT (ISBLANK(Account.Name))) && (MailingPostalCode <> Account.ShippingPostalCode)
Looks good and works well. 

Any thought?