Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Emma FayEmma Fay 
I'm working on the Admin Intermediate 'Create Validation Rules' challenge. https://trailhead.salesforce.com/content/learn/modules/point_click_business_logic/validation_rules?trail_id=force_com_admin_intermediate

This is the challenge:
- 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 saved
- 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 ISBLANKfunction for this check)

I'm presuming that to check whether the postal codes are the same you use "MailingPostalCode  =  Account.ShippingPostalCode"

It's the third step which is confusing me. So far my best guess is this, but I know it's wrong:
IF(ISBLANK(Account.ParentId) MailingPostalCode, MailingPostalCode  =  Account.ShippingPostalCode)

I basically want to say - if the field is blank, take no action. If it's not blank, check whether they're the same. If they're not the same, don't allow the record to be saved.

​​​​​​​Help!
 
Best Answer chosen by Jayson (salesforce.com) 
Andrew CookAndrew Cook
Hi Emma,

I used the following and it worked:

AND( 
NOT( ISBLANK ( Account.Id ) ), 
MailingPostalCode <> Account.ShippingPostalCode 
)
Neha KaushikNeha Kaushik 
I have created a field with a formula that calculates annual revenue. This considers probability(%)* monthly revenue* the number of months for which revenue is expected. I am able to do this part and this is sorted.
formula used: (13-MONTH( Est_Go_Live_Date__c ))* Amount * Probability

There is another field that captures the frequency of revenue as one-time and recurring.

Where I am facing challenges is:
I want when the frequency is one-time then it should show monthly revenue as is and where the frequency is recurring, the formula should come in effect. 
I tried doing this with formula-if but I am not able to get the right result. Please help if possible.
Best Answer chosen by Neha Kaushik
Aviral AgrawalAviral Agrawal
Check this one, 

IF(TEXT(Frequency__c) = "Recurring", ((13-MONTH( Est_Go_Live_Date__c ))* Amount * Probability),
IF(TEXT(Frequency__c) = "One-time",   Amount ,NULL))

 
Asmita PravinAsmita Pravin 
Hi
on my laptop screen, the "map" button is not occurring User-added image

due to this, I couldn't complete the task.
please help me
Thank you 
Best Answer chosen by Asmita Pravin
Manasa UdupiManasa Udupi
Hi Asmita,

Can you try to Zoom out ?
Brian ThurmanBrian Thurman 
The trailhead in question is: https://trailhead.salesforce.com/trails/learn-admin-essentials/projects/improve-data-quality-for-a-cleaning-supply-app/steps/create-a-formula-field

I have found a couple of other posts that describe identical acitivity to what is being requested, and it is a very simple thing.  The error message states "Formula in custom field 'Account Annual Revenue' is not correct. Check the instructions."

The actual formula  - 
Account.AnnualRevenue

-  being inserted from the list and following steps identically passes a syntax check and allows save, but the trailhead will not validate as complete stating the formula is wrong.
Best Answer chosen by Brian Thurman
Narender SinghNarender Singh
Hi Brian,

I helped someone with exact same issue in this post: https://success.salesforce.com/answers?id=9063A000000eKql

See if it helps.
Let me know if you still face the issue after going through it.
Bryan WiseBryan Wise 
I have challenge 3 working, but I'm getting an error while checking the challenge.  "There was an unhandled exception. Please reference ID: AJCMDZHO. Error: Faraday::ClientError. Message: 550: Cannot convert dynamic parameters of a reference line in chart widgets"

I'm wondering if this has anything to do with Spring 20 (which is awesome by the way).  I used the new binding builder to create a results binding for the dynamic reference line.
Best Answer chosen by Bryan Wise
Bryan WiseBryan Wise
Confirmed: this challenge does not work with the new dynamic reference lines in Spring 20.  I changed it to old school results binding and the challenge passed.  Here's the new syntax in spring that doesn't work:
"referenceLines": [
                            {
                                "label": {
                                    "data": {
                                        "displayTemplate": "[attrCost]",
                                        "sourceType": "result",
                                        "step": "Attrition_Cost_1"
                                    },
                                    "type": "dynamic"
                                },
                                "value": {
                                    "data": {
                                        "field": "attrCost",
                                        "sourceType": "result",
                                        "step": "Attrition_Cost_1"
                                    },
                                    "type": "dynamic"
                                }
                            }
                        ]

 
Kristina PandozziKristina Pandozzi 
I've gone through the steps of this section of the module 3 times now and everything seems to match up in my playground, but I an this error message stating, "Sean Forbes doesn't have access to the Edge SLA opportunity. Redo the steps to give him access."  I'm thinking it must having something to do with some detail outside of the actual steps provided in the module.  I'm trying to work through it... has anyone else experienced this and/or have any insight? Thanks!

 
Best Answer chosen by Jayson (salesforce.com) 
Anthony FosterAnthony Foster
This is still an issue as of August 4, 2019. I got around it by changing my Account OWD to read only and Opportunities to Public Read Write. Before trying this solution, I also tried manual sharing (available in classic only), setting the opportunity owner to Sean and then trying with the owner as Rose Gonzales (same as the edge installation opportunity).

Is there any way to notify Trailhead that something is not right?
LaTashia SmithLaTashia Smith 
I am on the Customize a SF Object > Create Picklists and Field Dependencies challenge and am running into this error message. I have checked it over and over and don't see why I am getting the error. User-added image
Best Answer chosen by Jayson (salesforce.com) 
Ron FeherRon Feher
SOLVED; sort of, I deleted the custom object that I had created and when I re-created it, after previewing the functionality of the picklist, it takes you out of lightning and into classic. The first time I escaped and went back to lightning; the second time I stayed in classic and finished the instructions and passed the module. Not sure if the switch to classic mattered but it solved it for me!
Best Answer chosen by Walther Matos
Jonathan FoxJonathan Fox
It sounds like a huge pain but log out, clear your browser cache and try again. Does that work?

If not, try spinning up a new trailhead playground and see if that allows you to do the challenge.
Chris DavisChris Davis 
Here I was cruising through this superbadge, and thought I was a click away from completing it, only to run into some strange goings on.  I completed step 1-6 no problem.  In one of the steps, I believe 5, we were to create a PB that, among other things, creates a Robo Setup record with the install date being 180 days beyond the closed date of the opportunity.  I've done that.  The requirements for step 7 are to make sure the install date does not land on a Saturday or Sunday.  I modified my action in my PB from [Opportunity].CloseDate + 180

to 

CASE(MOD([Opportunity].CloseDate + 180 - DATE(1900, 1, 7),7),
0, [Opportunity].CloseDate + 181,
6, [Opportunity].CloseDate + 182,
[Opportunity].CloseDate + 180)


I've gone through and created and Closed Won an Opportunity with a close date of every day of the week, and for each day of the week, a Robo Setup record is created with the date being 180 days in the future, unless it lands on a Saturday or Sunday, then the Date will be the following Monday. All tested properly. 

For my Day of the Week field, I'm using the formula:

CASE( MOD( Date__c - DATE(1900, 1, 7), 7), 0, "Sunday", 1, "Monday", 2, "Tuesday", 3, 
"Wednesday", 4, "Thursday", 5, "Friday", 6, "Saturday","Error")


Using this formula, the proper day of the week is displayed for all days of the week . 

So, I successfully completed all of the requirements of the challenge. When I click "Check Challenge", I get the error:

Challenge Not yet complete... here's what's wrong: 
The Robot Setup Day of the Week formula does not seem to be working properly. The Day of the Week should not fall on Saturday or Sunday.


At this point, I'm basically stuck.  The requirements of the challenge have been met, but I'm getting the above error even though the Day of the Week field functions properly.  Marking an Opp Closed Won will always create the Robo Setup record, assign the correct date and will always provide the correct day of the week. 

I assume at this point, it's no longer about meeting the "business requirements" and more about meeting whatever vague "trailhead requirements" are out there.  Since trailhead is not giving me a proper error, does anyone have any idea what else I can provide in order for it to complete the check? 

Thanks! 
Best Answer chosen by Chris Davis
Narender SinghNarender Singh
Hi,

Use this formula for "Day of the Week" field:
Case ( WEEKDay( Date__c ), 
1,"Sunday", 
2,"Monday", 
3,"Tuesday", 
4,"Wednesday", 
5,"Thursday", 
6,"Friday", 
7,"Saturday", 
Text(WEEKDay(Date__c)))

Now in your process for Robot Setup Object.

Criteria Node 1:
[Robot_Setup__c].Day_of_the_Week__c     EQUALS   String    Saturday

Action:
Update Records:

Date    FORMULA     [Robot_Setup__c].Date__c + 2


Criteria Node 2:
[Robot_Setup__c].Day_of_the_Week__c     EQUALS   String    Sunday

Action:
Update Records

Date    FORMULA     [Robot_Setup__c].Date__c + 1
Saransh PaliwalSaransh Paliwal 
Rule Name: Address_Validation
Error Condition Formula:
OR( 
AND( 
LEN(BillingState) > 2, 
NOT(CONTAINS(“AL:AK:AZ:AR:CA:CO:CT:DE:DC:FL:GA:HI:ID:IL:IN:IA:KS:KY:LA:ME:MD:MA:MI:MN:MS:MO:MT:NE:NV:NH:NJ:NM:NY:NC:ND:OH:OK:OR:PA:RI:SC:SD:TN:TX:UT:VT:VA:WA:WV:WI:WY”, BillingState )) 
), 
AND( 
LEN(ShippingState) > 2, NOT(CONTAINS(“AL:AK:AZ:AR:CA:CO:CT:DE:DC:FL:GA:HI:ID:IL:IN:IA:KS:KY:LA:ME:MD:MA:MI:MN:MS:MO:MT:NE:NV:NH:NJ:NM:NY:NC:ND:OH:OK:OR:PA:RI:SC:SD:TN:TX:UT:VT:VA:WA:WV:WI:WY”, ShippingState)) 
), 
NOT(OR(BillingCountry =”US”,BillingCountry =”USA”,BillingCountry =”United States”, ISBLANK(BillingCountry))), 
NOT(OR(ShippingCountry =”US”,ShippingCountry =”USA”,ShippingCountry =”United States”, ISBLANK(ShippingCountry))) 
)


Rule Name: Name_change
Error Condition Formula:
ISCHANGED(Name) && (ISPICKVAL(Type, “Customer – Direct”) || ISPICKVAL(Type, “Customer – Channel”))

Please tell me what is wrong in this
Best Answer chosen by Saransh Paliwal
Narender SinghNarender Singh
Ohh, you are doing the superbadge. :D

I did this one a long time ago.

Try this one:
( 
NOT((ShippingCountry = "US" || ShippingCountry = "USA" || ShippingCountry = "United States" || ISBLANK(ShippingCountry) )) 
|| 
NOT(( ShippingState= "AL" 
|| ShippingState= "AK" 
|| ShippingState= "AZ" 
|| ShippingState= "AR" 
|| ShippingState= "CA" 
|| ShippingState= "CO" 
|| ShippingState= "CT" 
|| ShippingState= "DE" 
|| ShippingState= "DC" 
|| ShippingState= "FL" 
|| ShippingState= "GA" 
|| ShippingState= "HI" 
|| ShippingState= "ID" 
|| ShippingState= "IL" 
|| ShippingState= "IN" 
|| ShippingState= "IA" 
|| ShippingState= "KS" 
|| ShippingState= "KY" 
|| ShippingState= "LA" 
|| ShippingState= "ME" 
|| ShippingState= "MT" 
|| ShippingState= "NE" 
|| ShippingState= "NV" 
|| ShippingState= "NH" 
|| ShippingState= "NJ" 
|| ShippingState= "NM" 
|| ShippingState= "NY" 
|| ShippingState= "NC" 
|| ShippingState= "ND" 
|| ShippingState= "OH" 
|| ShippingState= "OK" 
|| ShippingState= "OR" 
|| ShippingState= "MD" 
|| ShippingState= "MA" 
|| ShippingState= "MI" 
|| ShippingState= "MN" 
|| ShippingState= "MS" 
|| ShippingState= "MO" 
|| ShippingState= "PA" 
|| ShippingState= "RI" 
|| ShippingState= "SC" 
|| ShippingState= "SD" 
|| ShippingState= "TN" 
|| ShippingState= "TX" 
|| ShippingState= "UT" 
|| ShippingState= "VT" 
|| ShippingState= "VA" 
|| ShippingState= "WA" 
|| ShippingState= "WV" 
|| ShippingState= "WI" 
|| ShippingState= "WY" 
)) 
) 
|| 
( 
NOT((BillingCountry = "US" || BillingCountry = "USA" || BillingCountry = "United States" || ISBLANK(BillingCountry) ) ) 
|| 
NOT(( BillingState= "AL" 
|| BillingState= "AK" 
|| BillingState= "AZ" 
|| BillingState= "AR" 
|| BillingState= "CA" 
|| BillingState= "CO" 
|| BillingState= "CT" 
|| BillingState= "DE" 
|| BillingState= "DC" 
|| BillingState= "FL" 
|| BillingState= "GA" 
|| BillingState= "HI" 
|| BillingState= "ID" 
|| BillingState= "IL" 
|| BillingState= "IN" 
|| BillingState= "IA" 
|| BillingState= "KS" 
|| BillingState= "KY" 
|| BillingState= "LA" 
|| BillingState= "ME" 
|| BillingState= "MT" 
|| BillingState= "NE" 
|| BillingState= "NV" 
|| BillingState= "NH" 
|| BillingState= "NJ" 
|| BillingState= "NM" 
|| BillingState= "NY" 
|| BillingState= "NC" 
|| BillingState= "ND" 
|| BillingState= "OH" 
|| BillingState= "OK" 
|| BillingState= "OR" 
|| BillingState= "MD" 
|| BillingState= "MA" 
|| BillingState= "MI" 
|| BillingState= "MN" 
|| BillingState= "MS" 
|| BillingState= "MO" 
|| BillingState= "PA" 
|| BillingState= "RI" 
|| BillingState= "SC" 
|| BillingState= "SD" 
|| BillingState= "TN" 
|| BillingState= "TX" 
|| BillingState= "UT" 
|| BillingState= "VT" 
|| BillingState= "VA" 
|| BillingState= "WA" 
|| BillingState= "WV" 
|| BillingState= "WI" 
|| BillingState= "WY" 
)) 
)

This validation is for both shipping as well as billing.