>Create 2 custom fields of type Number on the Opportunity object: ‘radius’ with a resulting API name of ‘radius__c’ and ‘height’ with a resulting API name of ‘height__c’.
>The formula should be named ‘Cylinder Volume’, with the resulting API name ‘Cylinder_Volume__c‘ and should be created on the Opportunity object.
>The formula should reference the custom fields ‘radius__c‘ and ‘height__c‘.
>The formula should use 3.14159 as an approximation of Pi.
Heres the challenge that im stuck on. i have created the 2 custom fields. What im stuck on is where do we create the formula. Do we put it in the custom fields or is there another place u insert it?
thanks if anyone can help
"Challenge Not yet complete... here's what's wrong:
The validation rule does not reference the 'IsClosed' and 'CloseDate' fields correctly. Take a look at the requirements again."
Here is the challenge:
Your number-crushing sales team has so many deals in the pipeline, you’re starting to see occasional problems with data quality. Namely, sales reps are forgetting to update the close date to a date in the future. Make a formula that requires an opportunity to have a CloseDate of today or any future date. Hint: this formula should reference the hidden IsClosed checkbox field on the Opportunity object, and you will be creating the formula as an Opportunity validation rule.The validation rule should be on the Opportunity object
The validation rule should be named 'Close_Date_Alert'
The validation rule should fire if IsClosed is not selected and CloseDate is yesterday or earlier
The validation rule should display the error 'Hey McFly, unless you are planning to go back in time, please update your close date' at the top of the page when triggered
Here is the formula I currently have in there:
CloseDate < TODAY() && NOT(IsClosed)
I have probably written this like 10 diffrent ways and cant get it to properly validate.
I'm struggling with the logic of the task...
To complete this challenge, add a validation rule which will block the insertion of a contact if the contact is related to an account and has a mailing postal code (which has the API Name MailingPostalCode) different from the account's shipping postal code (which has the API Name ShippingPostalCode).Name the validation rule 'Contact must be in Account ZIP Code'.
A contact with a MailingPostalCode that has an account and does not match the associated Account ShippingPostalCode should return with a validation error and not be inserted.
The validation rule should ONLY apply to contact records with an associated account. Contact records with no associated parent account can be added with any MailingPostalCode value. (Hint: you can use the ISBLANK function for this check)
Here is what I got so far:
MailingPostalCode <> Account.ShippingPostalCode )
I THINK I know how to see if the contact mailing zip is not the same as the account shipping zip, and only if the is not blank.
The part I am stuck on is if the "Contact records with no associated parent account can be added with any MaiilingPostalCode value"...
I don't know what to do with that.
Also, I am now getting the error message when I recheck challenge:
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, Contact_must_be_in_Account_ZIP_Code: 
Double help, please.