Hello, 

The challenge has asked for the following: 
Create an OData 2.0 external data source with 'Mobile Devices' as the label, 'Mobile_Devices' as the name, and this URL: https://phone-odata-demo.herokuapp.com/devices.svc/
Use the 'AtomPub' format and the 'Anonymous' Identity Type for the 'Mobile Devices' External Data Source.
The 'Mobile Devices' data source must validate and sync the 'phone_plans' table to result in an external object with the API name 'Phone_Plan__x'.
The 'Mobile Devices' data source must validate and sync the 'phones' table to result in an external object with the API name 'Phone__x'.
Note that you will need to adjust the Object Names for the two external objects from the default setting after the initial sync.



I have reread the instructions and for some reason I'm still getting the error below. I noticed that others who have done this challenge have the value "Lightning Connect: OData 2.0" in the Type field while I don't have that as an option and can only select "Salesforce Connect: OData 2.0". Any ideas? 

With all this Process Orchestration on new Lightning Flow Builder, I can see how the business will shoot itself in a foot but building massive complex processes by using some contracted developers, then pile feature phase nobody will know how the complexity of work. When multiple devs contracted in small itterations to add features eventually nobody can track how all these systems and events fit together. that will lead to attempts to build some complex process visualization tools similar to data model schemas or process diagrams.

I continue to see this Conflict error with DX force:source:push/pull command, do not know how to solve this problem.
Doing Trailhead module to learn more DX skills: Get Started with Salesforce DX  App Development with Salesforce DX get stuck on pushing code to scratch org. Any step requiring a command to push/pull code sfdx force:source:push/pull end with conflict errors and code is NOT added to scratch org.
I have these layouts and objects in my ScratchOrg and local source code, following steps in a module ends with this error. I do not see any way to solve this other than restart project from 0. I did several steps
1. Try to delete Conflicting metadata from local - DID NOT HELP
2. Try to PULL source from ORG to refresh - DID NOT HELP (get same conflict error)
4. Checked my file paths in .sfdx/orgs/test-xxxxxxx/sourcePathInfos.json - all file paths are correct
5. Try to delete conflicted metadata refs inside .sfdx/orgs/test-xxxxxxx/sourcePathInfos.json - THIS STOPS CONFLICT BUT NO METADATA IS UPDATED
Anyone knows how to fix this DX error?
fdx force:source:push
STATE     FULL NAME               TYPE           PROJECT PATH
────────  ──────────────────────  ─────────────  ────────────────────────────────────────────────────────────────────────
Conflict  Account-Account Layout  Layout         force-app/main/default/layouts/Account-Account Layout.layout-meta.xml
Conflict  Geolocation             PermissionSet  force-app/main/default/permissionsets/Geolocation.permissionset-meta.xml
Conflict  Account                 CustomObject   force-app/main/default/objects/Account.object-meta.xml

Getting build error while using Mobile iOS SDK ServiceCloud snapins for Knowledge or Service/Case.
Trying to build the app for iOS 10.3 Xcode 8.3.2 Swift 3 using Service mobile SDK. Initially following quick start guide app worked in the simulator. But once I try to load it iPhone device started to get errors. Now even trying a build for simulator throws the same error. I found It is Swift-Obj-C bridging header and Framework issue. I try several workarounds, settings in Xcode to "Allow non-modular header" Bitcode=On/OFF etc. but nothing works. Any ideas how to fix this?
Error:
ServiceKnowledge.framework/Frameworks/KnowledgeCore.framework/Headers/SCDefines.h:28:9: Include of non-modular header inside framework module 'ServiceKnowledge.KnowledgeCore.SCDefines': '/Users/mobile/mobile-sf-service/Pods/Headers/Public/ServiceSDK/SalesforceSDKCore/SalesforceSDKCore.h'

After read forums seem I am not only one with this error, on challenge step Map Your Workflow Criteria to Process Criteria. I have tested on New Playground, New DE org just fro this and existing Playground sill get this error. I see some people passed this module make me wonder what is wrong here?

Challenge Not yet complete... here's what's wrong: 
There was an unexpected error while verifying this challenge. Usually this is due to some pre-existing configuration or code in the challenge Org. We recommend using a new Developer Edition (DE) to check this challenge. If you're using a new DE and seeing this error, please post to the developer forums and reference error id: SYLWGDVP

We have a web app that uses salesforce Communities as IDP to register and authenticate users via OAuth 2.0.
Set up connected app for this with correct OAuth settings, redirect URL for testing with http:localhost NOT https yet. Wen use connected app in mode all users are Perauthorized with admin (avoid that Authorize app poopup). We set startURL parameter to eredirect user to our web -app after Community login or register.
Login existing user works as expected user authenticates and redirected to the app with Access token - GREAT!
Now Registration new user - DO NOT WORK. It seem new user is created but automated-login for this new user always redirects user to Community portal Home page. Even we set StartURL to our direct to http://localhost:8080... still Community page. Try to change APEX controller to force redirect still not working. Site.login method seem to NOT responding to startURL when Connected app is set PRE AUTHORIZED.

On other hand if I switch connected app to Allow all users to Self authorize then Site.login redirects to our Web-app via startURL.

Is this some Limitation that makes use of connected app with web-apps painfull? Bad UX requiring some additional steps.
May this is some Comunity bug? Any insight will be helpfull.
Thank you

I keep getting this error on Trailhead module  - Map Your Workflow Criteria to Process Criteria. After using my DE org failed on this error I try to set New Playground, followed all instructions and still get this error
Challenge Not yet complete... here's what's wrong: 
There was an unexpected error while verifying this challenge. Usually, this is due to some pre-existing configuration or code in the challenge Org. We recommend using a new Developer Edition (DE) to check this challenge. If you're using a new DE and seeing this error, please post to the developer forums and reference error id: SRLTJCIY

May be this does not work on Playground and need to provision Brand new DE with MayDomain and Lightning? Trail not saying anything on this?
 

I was able to build the Trailhead VR project and test it in UNITY all seem to work ok. Module uses Android example but I built the app for iOS platform and loaded to iPhone 6S iOS 10.1, the app works displaying Opptys but the view is cut off. I am not sure if this is camera view setup in Unity or some iOS build setting?

Anyone has a solution to the deployment error on SearchLayouts various AdditionalFields like lookupPhoneDialogsAdditionalFields & <lookupFilterFields>?
Problem: Object Metadata uses ORG dependent Field IDs for custom Fields in XML files
<lookupFilterFields>00N6100000DVxaw</lookupFilterFields><lookupPhoneDialogsAdditionalFields>00N2C000000HWex</lookupPhoneDialogsAdditionalFields>

While Standard fields look this way: <lookupFilterFields>OPPORTUNITY.NAME</lookupFilterFields>
These references make it impossible to deploy on various sandboxes.
 Look like a Salesforce BUG

There is a typo in Create a Satisfaction Survey Project 1st step describes Text Area Long field but no details given instead it mixes instruction for Tab. You get this error: Challenge Not yet complete... here's what's wrong: 
The Comments field is either missing or not properly created. Please check instructions. 
Note: you may run into errors if you've skipped previous steps.

Obvious solution to make a field name: Comments - Long Text Area

I have written test class, earlier it was working fine. Now to enhance it I have edited class and when i am trying to save it is throwing error like'Test.setFixedSearchResults is not a valid method or not valid signature'.

Please help me.

Is there a way to send user authentication information as part of the request URL to a VisualForce page?  The page I'm developing has a report chart on it, so I can't just rely on the Guest User profile since it doesn't allow running of reports.   I'd like to create a user with a very restricted profile and access to a small number of reports, and then be able to render the Visualforce page as if that user was logged in.  I don't want the site visitor to have to provide login credentials.     

Is it possible to have a custom web service send back a report chart in its response?   If so, would love at least some high-level steps on how to accomplish this.

Hello, I am hoping that somebody can help me out with a very slow first REST call to our SalesForce test instance. 

We have boiled it down to a few cURL calls for reproducibility. Unfortunately, it is reproducible every day - but only once, after the first slow REST call, all subsequent calls are fast. The first API call to authenticate is fast, but the first to query the /services/data/v39.0/query API is slow. It appears that the instance is warming or caching somehow, but we can't find any documentation about this.

Has anybody seen anything like this before? 30s calls are just too slow for a simple select.

Thanks,
Grant
 
Steps for reproducing -
First, we authenticate:

curl -v --trace-time -X POST https://test.salesforce.com/services/oauth2/token  -H 'content-type: multipart/form-data'  -F grant_type=password  -F client_id=<snip>    -F client_secret=<snip>  -F username=<snip>    -F password=<snip>

cURL verbose of that call:

10:12:09.125368 * About to connect() to test.salesforce.com port 443 (#0)
10:12:09.125867 *   Trying 136.147.58.173...
10:12:09.147686 * Connected to test.salesforce.com (136.147.58.173) port 443 (#0)
10:12:09.148953 * successfully set certificate verify locations:
10:12:09.149214 *   CAfile: none
  CApath: /etc/ssl/certs
10:12:09.149905 * SSLv3, TLS handshake, Client hello (1):
10:12:09.171806 * SSLv3, TLS handshake, Server hello (2):
10:12:09.172253 * SSLv3, TLS handshake, CERT (11):
10:12:09.174550 * SSLv3, TLS handshake, Server finished (14):
10:12:09.175193 * SSLv3, TLS handshake, Client key exchange (16):
10:12:09.175473 * SSLv3, TLS change cipher, Client hello (1):
10:12:09.176019 * SSLv3, TLS handshake, Finished (20):
10:12:09.196838 * SSLv3, TLS change cipher, Client hello (1):
10:12:09.197305 * SSLv3, TLS handshake, Finished (20):
10:12:09.197607 * SSL connection using AES256-SHA
10:12:09.197919 * Server certificate:
10:12:09.198192 *        subject: C=US; ST=California; L=San Francisco; O=Salesforce.com, Inc; OU=Applications; CN=test.salesforce.com
10:12:09.198481 *        start date: 2015-06-05 00:00:00 GMT
10:12:09.198741 *        expire date: 2018-06-04 23:59:59 GMT
10:12:09.199137 *        subjectAltName: test.salesforce.com matched
10:12:09.199435 *        issuer: C=US; O=Symantec Corporation; OU=Symantec Trust Network; CN=Symantec Class 3 Secure Server CA - G4
10:12:09.199793 *        SSL certificate verify ok.
10:12:09.200266 > POST /services/oauth2/token HTTP/1.1
10:12:09.200266 > User-Agent: curl/7.29.0
10:12:09.200266 > Host: test.salesforce.com
10:12:09.200266 > Accept: */*
10:12:09.200266 > Content-Length: 712
10:12:09.200266 > Expect: 100-continue
10:12:09.200266 > content-type: multipart/form-data; boundary=----------------------------5f6c77e4d919
10:12:09.200266 >
10:12:09.218608 < HTTP/1.1 100 Continue
10:12:09.592160 < HTTP/1.1 200 OK
10:12:09.592452 < Date: Wed, 03 May 2017 15:12:19 GMT
10:12:09.592745 < Strict-Transport-Security: max-age=31536000; includeSubDomains
10:12:09.593017 < X-Content-Type-Options: nosniff
10:12:09.593286 < X-XSS-Protection: 1; mode=block
10:12:09.593539 < Content-Security-Policy: reflected-xss block;report-uri /_/ContentDomainCSPNoAuth?type=xss
10:12:09.593784 < Content-Security-Policy: referrer origin-when-cross-origin
10:12:09.594033 < Set-Cookie: BrowserId=<snip>;Path=/;Domain=.salesforce.com;Expires=Sun, 02-Jul-2017 15:12:19 GMT
10:12:09.594283 < Expires: Thu, 01 Jan 1970 00:00:00 GMT
10:12:09.594630 < Pragma: no-cache
10:12:09.594894 < Cache-Control: no-cache, no-store
10:12:09.595144 < X-ReadOnlyMode: false
10:12:09.595406 < Content-Type: application/json;charset=UTF-8
10:12:09.595671 < Vary: Accept-Encoding
10:12:09.595920 < Transfer-Encoding: chunked
10:12:09.596204 <
10:12:09.596619 * Connection #0 to host test.salesforce.com left intact

 
Returning:

{"access_token":"<snip>","instance_url":"https://cs54.salesforce.com","id":"<snip>","token_type":"Bearer","issued_at":"<snip>","signature":"<snip>"}

From here, we attempt a simple select Id limit 1, but it takes almost 30 seconds:

curl -v --trace-time -X GET \
'https://cs54.salesforce.com/services/data/v39.0/query?q=SELECT%20Id%20FROM%20Account%20LIMIT%201' \
  -H 'authorization: Bearer <snip>

 
Verbose (don't worry about the time this was run - 3p vs 10a, we are concerned about the time from intialization to return):

curl -v --trace-time -X GET \
>  'https://cs54.salesforce.com/services/data/v39.0/query?q=SELECT%20Id%20FROM%Account%20LIMIT%201' \
>   -H 'authorization: Bearer <snip>
15:03:54.066383 * About to connect() to cs54.salesforce.com port 443 (#0)
15:03:54.066855 *   Trying 136.147.103.22...
15:03:54.104193 * Connected to cs54.salesforce.com (136.147.103.22) port 443 (#0)
15:03:54.105318 * successfully set certificate verify locations:
15:03:54.105583 *   CAfile: none
  CApath: /etc/ssl/certs
15:03:54.106125 * SSLv3, TLS handshake, Client hello (1):
15:03:54.142363 * SSLv3, TLS handshake, Server hello (2):
15:03:54.142774 * SSLv3, TLS handshake, CERT (11):
15:03:54.144940 * SSLv3, TLS handshake, Server finished (14):
15:03:54.145588 * SSLv3, TLS handshake, Client key exchange (16):
15:03:54.145858 * SSLv3, TLS change cipher, Client hello (1):
15:03:54.146462 * SSLv3, TLS handshake, Finished (20):
15:03:54.185332 * SSLv3, TLS change cipher, Client hello (1):
15:03:54.185789 * SSLv3, TLS handshake, Finished (20):
15:03:54.186074 * SSL connection using AES256-SHA
15:03:54.186335 * Server certificate:
15:03:54.186606 *        subject: C=US; ST=California; L=San Francisco; O=Salesforce.com, Inc; OU=Applications; CN=*.salesforce.com
15:03:54.186889 *        start date: 2015-02-14 00:00:00 GMT
15:03:54.187141 *        expire date: 2018-02-14 23:59:59 GMT
15:03:54.187421 *        subjectAltName: cs54.salesforce.com matched
15:03:54.187692 *        issuer: C=US; O=Symantec Corporation; OU=Symantec Trust Network; CN=Symantec Class 3 Secure Server CA - G4
15:03:54.188013 *        SSL certificate verify ok.
15:03:54.188432 > GET /services/data/v39.0/query?q=SELECT%20Id%20FROM%Account%20LIMIT%201 HTTP/1.1
15:03:54.188432 > User-Agent: curl/7.29.0
15:03:54.188432 > Host: cs54.salesforce.com
15:03:54.188432 > Accept: */*
15:03:54.188432 > authorization: Bearer <snip>
15:03:54.188432 >
15:04:11.267080 < HTTP/1.1 200 OK
15:04:11.267389 < Date: Wed, 03 May 2017 20:04:04 GMT
15:04:11.267633 < X-Content-Type-Options: nosniff
15:04:11.267900 < X-XSS-Protection: 1; mode=block
15:04:11.268178 < Content-Security-Policy: reflected-xss block;report-uri /_/ContentDomainCSPNoAuth?type=xss
15:04:11.268423 < Content-Security-Policy: referrer origin-when-cross-origin
15:04:11.268659 < Set-Cookie: BrowserId=<snip>;Path=/;Domain=.salesforce.com;Expires=Sun, 02-Jul-2017 20:04:04 GMT
15:04:11.268894 < Expires: Thu, 01 Jan 1970 00:00:00 GMT
15:04:11.269139 < Sforce-Limit-Info: api-usage=34/5000000
15:04:11.269380 < Content-Type: application/json;charset=UTF-8
15:04:11.269616 < Vary: Accept-Encoding
15:04:11.269852 < Transfer-Encoding: chunked
15:04:11.270089 <
15:04:11.270493 * Connection #0 to host cs54.salesforce.com left intact

Returning:

{"totalSize":1,"done":true,"records":[{"attributes":{"type":"<snip>","url<snip>"},"Id":"<snip>"}]}

 

We have a web app that uses salesforce Communities as IDP to register and authenticate users via OAuth 2.0.
Set up connected app for this with correct OAuth settings, redirect URL for testing with http:localhost NOT https yet. Wen use connected app in mode all users are Perauthorized with admin (avoid that Authorize app poopup). We set startURL parameter to eredirect user to our web -app after Community login or register.
Login existing user works as expected user authenticates and redirected to the app with Access token - GREAT!
Now Registration new user - DO NOT WORK. It seem new user is created but automated-login for this new user always redirects user to Community portal Home page. Even we set StartURL to our direct to http://localhost:8080... still Community page. Try to change APEX controller to force redirect still not working. Site.login method seem to NOT responding to startURL when Connected app is set PRE AUTHORIZED.

On other hand if I switch connected app to Allow all users to Self authorize then Site.login redirects to our Web-app via startURL.

Is this some Limitation that makes use of connected app with web-apps painfull? Bad UX requiring some additional steps.
May this is some Comunity bug? Any insight will be helpfull.
Thank you

A Create a Record action for the Closed Won criteria node isn’t properly configured. Make sure that it creates a task and uses the same field settings as the ‘Follow up on new contract’ task action. Make sure that Due Date Only is set by using a formula.


Hep me for this Problem!

I've tried a second time using a brand new Trailhead Playground, and still get the error when checking the challenge:
"Challenge Not yet complete... here's what's wrong: 
There was an unexpected error while verifying this challenge. Usually this is due to some pre-existing configuration or code in the challenge Org. We recommend using a new Developer Edition (DE) to check this challenge. If you're using a new DE and seeing this error, please post to the developer forums and reference error id: VRHJDGJD "

Hello, 

The challenge has asked for the following: 
Create an OData 2.0 external data source with 'Mobile Devices' as the label, 'Mobile_Devices' as the name, and this URL: https://phone-odata-demo.herokuapp.com/devices.svc/
Use the 'AtomPub' format and the 'Anonymous' Identity Type for the 'Mobile Devices' External Data Source.
The 'Mobile Devices' data source must validate and sync the 'phone_plans' table to result in an external object with the API name 'Phone_Plan__x'.
The 'Mobile Devices' data source must validate and sync the 'phones' table to result in an external object with the API name 'Phone__x'.
Note that you will need to adjust the Object Names for the two external objects from the default setting after the initial sync.



I have reread the instructions and for some reason I'm still getting the error below. I noticed that others who have done this challenge have the value "Lightning Connect: OData 2.0" in the Type field while I don't have that as an option and can only select "Salesforce Connect: OData 2.0". Any ideas? 

I am stuck doing this challenge. I've installed the package but when I am trying to add a lightning component I get this error

reference error id: DPFVJULB 

All modules (before and after this one) verify fine!  The flow works perfectly.  However, this one will not verify...I get an error that tells me to try it in a new DE.  I hate to start over and get the same issue when everything around it works fine.  Is it just me?

I Just wanted to know what is Salesforce TrailHeadDX ? How can i learn ? 

Hi folks,
I've a general question for the following usecase:

... I have two custom objects A and B.
... A has a lookup field to B.
... I wanna create / insert a new A object that contains a new B object
... while the iOS device is in an offline state
... with the SmartStorage / SmartObjects
... from the native mobile SDK for iOS

It would be great if you could provide me some information or search query words to learn more about how I have to implement my quries, requests or app logic to fullfill the abovementioned requirements.

Kind regards,
- Tobi

When someone takes the time/effort to repspond to your question, you should take the time/effort to either mark the question as "Solved", or post a Follow-Up with addtional information.  

 

That way people with a similar question can find the Solution without having to re-post the same question again and again. And the people who reply to your post know that the issue has been resolved and they can stop working on it.