
The instructions require that I copy a JSON code into the analytics filter as follows:
{'datasets': {'DTC_Opportunity_SAMPLE': [{'fields': ['Account_Name'], 'filter': {'operator': 'matches', 'values': ['$Name']}}]}}
It even recommends copying and pasting this code as even a small mistake will result in error. I have done that - I've copied and pasted it several times over, saved, and activated.
I can see the accurate result of this module because when I then go back to various accounts the JSON code works functionally and depending on which account I'm looking at the wave dashboard displays different results.
When I go to verify I get this message:
The filter doesn't match the JSON string in the instructions. Check your filter carefully. Even one character missing or out of place can cause problems.
I decided to just create a new dev org and re-do this module and following the same exact method of handling the issue. Now I'm getting this error message:
We can't find the account record page. Make sure that you’re using your Analytics-enabled Developer Edition org and that you’re in the Sales app.
I know with certainty that I've activated an analytics enabled org and that I'm in the Sales app.
Is this a buggy module? I didn't get a single hit when I googled these error messages so it seems that nobody else is having this issue.... help?
I solved this issue by following this steps:
- In Dashboard filters instead of Filter Builder switch to Filter String
- Fill text area fill the following code:
{'datasets': {'DTC_Opportunity_SAMPLE': [{'fields': ['Account_Name'], 'filter': {'operator': 'matches', 'values': ['$Name']}}]}}
As I see it the problem is in incorrect convertion of filter condition. It expect matches but get in value insted.
@Aleksandr Pashkin new org for the win. Thank you much, that closes out the last badge and module. In a new DE org, the winning json
{"datasets":{"DTC_Opportunity_SAMPLE":[{"fields":["Account_Name"],"filter":{"operator":"matches","values":["$Name"]}}]}}
Same problem for me. I think this is a broken module. Does anyone know how to put in a ticket for broken trailhead modules? After many many attempts i was finally successful, what i did was
1. clicked +Add data set builder
2. changed the defaults (Opportunity Name) to select (Account Name)
and ensure operator is "Equals"
3. Select Object Field to Account Name
4. hit Tab three times in my keyboard until i see the OK button. (this was the step which get me to the OK button, which otherwise is not vissible)
and save and it worked for me and was able to pass the challenge.
Thanks @Jim Taber @Aleksandr Pashkin for the tip to explore options.
notice: when i checked the filter string, i see it as below, with "locked" : null and "hidden" : null (little extension in my filter string) and my operator as "in" instead of matches.
not sure if the issue is always different for each one but I have attached my steps if this might help
{"datasets":{"DTC_Opportunity_SAMPLE":[{"fields":["Account_Name"],"filter":{"operator":"in","values":["$Name"]},"locked":null,"hidden":null}]}}
{"datasets":{"DTC_Opportunity_SAMPLE":[{"fields":["Account_Name"],"filter":{"operator":"in","values":["$Name"]}}]}} I've open a ticket and the support told me to recreate a new org and it has been ok for me. The Json to copy/paste was ok, but my org was not in good shape. With a new org i've validated my badge I also faced this error when I was using my existing Developer Org. I tried to follow the instructions on this module many times , but still show the exact same error. Here is what I did to finish this module.I created a new Developer org and tried to re-do with their instructions again and it worked smoothly and finally I'm able to complete this module.
Thanks @Aleksandr Pashkin for the tip. It worked for me. 'matches' translated to 'contains' and 'in' translated to equals in the filter. I created a new developer org and completed just the last section of this module and it worked. Thanks! Facing the same issue