Skip to main content

#Trailhead Challenges1.653 diskutieren mit

Hands-on challenges are the “secret sauce” of Trailhead. Before searching for solutions to superbadge challenges, review the Salesforce Certification Program Agreement and Policies. ** NOTE ** : If you were able to get a response that solved your issue, please mark it as the 'Best Answer' to help other Trailblazers. If the issue persists after 48 hours, create a Trailhead Help case at https://help.salesforce.com/s/support for further assistance.
0/9000

I've encountered an error on the last part of getting external services badge. Here is what the error states:   

We can't find the correct settings in the 'Bank Account Updated?' decision. Make sure it was created according to the requirements, including correct target references for 'account created' (pointing to the Update_Salesforce_User_Record Update Records step) and 'Bank Account Found' (pointing to the Assign_Existing_Bank_Account_ID Assignment step).  Attached here is the flow that I have created. 

Problem in External Services Use External Services in a Flow Trail

  

24 Antworten
  1. 15. Dez. 2021, 23:25

    i think you need to drag a line from the "Bank Account Updated? decision element to the "Update Records" element that skips the assignment for the "Bank Account Created" decision fork.

0/9000

Hi.  I have a question about the "Create a flow using an external service action" challenge in the "Using external services in a flow" section of the Trailhead "Intermediate System Administrator" course. 

I followed the instructions to set it up, but when I debug the flow I get an error saying "Conflict." 

The same error occurred even after creating a new Playground. 

for some reason the challenge itself is passed. 

I would be grateful if you could let me know how to solve the above problem. Thank you in advance. 

 

<Error details during debugging> 

BANKSERVICE.ADDACCOUNT (EXTERNAL SERVICES):

Add Bank Account 

Inputs:

 

accountName = {!Last_Name_on_Account} (Thompson) 

accountType = {!Bank_Account_Type} (Checking)

Error Occurred: Conflict 

 

<Contents of received email> 

You’ve received this email because an error occurred while your "Bank Account Records" flow was running. Debug this flow in Flow Builder. 

 

Error element Add_Bank_Account (FlowActionCall). 

Conflict     

4 Antworten
0/9000

Getting and error in the callout to create account BankService.addAccount  

 

 "We couldn't run action

BankService.addAccount

because something went wrong." 

 

Has anyone come across this one and managed to find a solution? 

Create a Flow Using External Services Actions

 

 

 

#Trailhead Challenges

15 Antworten
0/9000
  1. From Setup, enter Flow in the Quick Find box, then select Flows.
  2. Click New Flow.
  3. Make sure Start from Scratch is selected, and click Next.
  4. Select Screen Flow and click Create.
  5. In the button bar, change the Auto-Layout setting to Free-Form.
  6. From the toolbox, with the Elements tab selected, drag Action onto the canvas.
  7. To see the actions imported by External Services based on the API spec we used in the previous step, change Filter By to Type, select External Service, and click in the search box.

When I change filter to type, I don't see an option for external service, I've attached a screenshot

 

#Trailhead Challenges

6 Antworten
  1. 25. Juni 2024, 07:35

    Hi, @Rebecca Aramandla

     

    Yes, indeed you are missing the "External Service" type. To create it, you need to follow the steps described in this Challenge. 

    https://trailhead.salesforce.com/content/learn/projects/use-external-services-with-a-flow/register-external-service

     

    1. Click Gear Icon --> Setup --> In the search field type "named credentials" and select it --> Click New -> New LegacyHi, Yes, indeed you are missing the

    1. From Setup, enter Named Credentials in the Quick Find box, and select Named Credentials.
    2. From the dropdown menu next to the New button, select New Legacy.
    3. For Label, enter Bank.
    4. For Name, enter Bank (in English).
    5. For URL, enter https://th-external-services.herokuapp.com
    6. Leave other fields as they are and click Save.

    After them:

     

    1. From Setup, enter External Services in the Quick Find box, then select External Services.
    2. Click Add an External Service.
    3. On the Select an API Source page, select From API Specification.
    4. Click Next.
    5. For External Service Name, enter BankService (no space).
    6. For Select a Named Credential, select Bank (the Named Credential we just created).
    7. For Service Schema select Relative URL.
    8. For URL enter /accounts/schema. This string is added to the Named Credential we just made. It's the relative URL that points to the API spec. Together, they form the full URL from our service provider. For example: https://th-external-services.herokuapp.com/accounts/schema.
    9. Click Save & Next.
    10. Select all of the Operations.
    11. Click Next. A list of External Service Actions appears. These actions are now available to you in Flow Builder. Use the scrollbar to view them all. The operations in your API spec have now become invocable actions in Salesforce.
    12. Click Finish.

     

    After that, you will be able to continue with your next Challenge: 

    https://trailhead.salesforce.com/content/learn/projects/use-external-services-with-a-flow/access-external-business-actions

     

    Sincerely, 

    Mykhailo Vdovychenko 

    Bringing Cloud Excellence with IBVCLOUD OÜ

0/9000

Hello 

Got error when performed run for the Flow "Bank Account Records". Please can you guide how to resolve this. 

"Use External Services With a Flow -> Create a Flow Using External Services Actions 

-> Debug Your Flow" 

Error : An unhandled fault has occurred in this flow 

An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. 

 

#Trailhead Challenges

7 Antworten
  1. 10. Jan., 17:28

    @Ajay Tiwari when the External Service isn’t set up exactly the way Trailhead expects. 

    First, double-check that the External Service was registered successfully and that all actions are available in Flow. Then open the flow and make sure every required input for the External Service action is mapped correctly — even one missing or wrong data type can cause this generic fault.

0/9000