#Httpcallout0 人がディスカッション中

The response I get from a HTTP callout I want to use from Flow looks like this JSON:

[{"attributes":{"key1":numvalue,"key2":"txtvalue","key3":"txtvalue"}}]

Because the values I want to use are enumerated under "attributes", currently the new "Transform" Flow element won't let you map these values directly to a record's fields:  

When mapping a field in a source collection to a field in the target collection, both collections must be at the same hierarchical level in their respective resource. For example, the 2XX collection and the Order collection aren’t within any other collection. Because they’re both the top collections in their respective resources, you can map fields between them.

Is there any sensible workaround to adjust the returned info so that it can be mapped to record fields with the "Transform" element? Or is Flow just not capable of that kind of thing yet, and I should just manually parse the JSON string myself? (Yes, there are USF tools that'll do that, it would be nice if I could just get past this one roadblock with native features, though.)

#Flow #Httpcallout #Integration

Hello,

I am using Open API 3.0 to connect two Salesforce orgs. I have a scenario where,

Let's say

1. Source Org Account Name : Salesforce, USA
2. Target Org Account Name: Salesforce, USA

There is a duplicate rule in Target Org which doesn't allow us to create the accounts with the same names.

So, when I tried to push the source org record to Target org and I got the error as ( 400 response code)

Result: [{
"message_set" : true,
"message" : "Please choose one of these records instead.",
"errorCode_set" : true,
"errorCode" : "DUPLICATES_DETECTED"
}]

My questions are,

1. Is there anyway to get extract message only from the response?
2. Is there anyway to get the duplicate record Id from the Target org which I can update the Id back to one of the Account's fields in source org?

The response result doesn't return any details apart form the above message so that makes hard for me to refer the target org accountId.

Thank you in advance.

#HTTP POST Method #Httpcallout #Flow

Looking for an easy way to bring external data into Flow?

An open Beta of the no-code HTTP Callout is coming in Spring ‘23, empowering you to integrate Flow with external systems faster than ever before. HTTP Callout reduces your reliance on a developer and enables you to build the action right within Flow Builder.

Join the @Flow HTTP Callout group to:

• get resources for getting started
• share feedback with the product team
• learn from the community

We can’t wait to hear about your first use cases for automating processes with external data!

#httpcallout