Working for customer integration here is what I am trying to achieve
Source API returns array of data in response.
Destination App API can accept only one record at time. Basically it means I need to create multiple request but one by one and send it to destination app. Kind of For Each loop
I am sure there is something which should be simple but I don't understand the setup parameter in Celigo.
Please help me with the setup or link me the document to solve this.
Thanks
Hello Sachin -
What are the APIs (Source & Destination) you are working with?
Hi Andrew
On the source we have Celigo State API.
On the destination we have 2 lookups and 1 import.
Out of 2 lookup the one which I am interested here is the last one.
It accepts XML and respond XML. The response has multiple data which I want to pass down stream one by one. I was hoping that page size = 1 on the lookup will send the data to import one by one. I am expecting multiple request for import with this configuration
My understanding is page size on export ( lookup here) should the send the data down stream packaging as one record per page.
However when I run the flow and debug the lookup and import I don't see multiple request on import, also when I see under pages heading for lookup in Dashboard it has value 1. I think the count should be number of records return in response of lookup as page size is 1.
Please let me know if it explains the picture.
Thanks
Sachin
Hi @sachinkumarrana,
It's still not quite clear to me. Could you post a screenshot of your flow in Flow Builder, what you have set in your export and what preview you're getting, as well as what you're getting in the lookup and what you're getting when you run the flow versus what you expect? What mapping are you doing? Do you have any hooks or filters applied? There are several factors to consider. Make sure to hide any PII before posting. Thanks!
Hi @sachinkumarrana,
In your import, do you have your One-to-many option set to No? If so, try using the One-to-many option set to Yes (Advanced). If that doesn't work, please provide the information I asked for above to help us understand your issue better. Thanks!
Hi Courtney,
3rd Step: QXTEND Bank Create API
************************************
The response preview
{
"page_of_records": [
{
"record": {
"$": {
"xmlns:ns1": "urn:schemas-qad-com:xml-services"
},
"ns1:ttRBankTransaction_ID": [
{
"_": "5617-536d-4f73"
}
],
"ns1:ttRCardknoxTransaction_ID": [
{
"_": "448959968"
}
],
"ns1:ttRBankStateLineNumber": [
{
"_": "1"
}
],
"ns1:tt_result": [
{
"_": "Error"
}
],
"ns1:tt_message": [
{
"_": " Invalid Customer code "
}
]
}
},
{
"record": {
"$": {
"xmlns:ns1": "urn:schemas-qad-com:xml-services"
},
"ns1:ttRBankTransaction_ID": [
{
"_": "391a-8a5a-40d4"
}
],
"ns1:ttRCardknoxTransaction_ID": [
{
"_": "451083116"
}
],
"ns1:ttRBankStateLineNumber": [
{
"_": "1"
}
],
"ns1:tt_result": [
{
"_": "Error"
}
],
"ns1:tt_message": [
{
"_": " Invalid Customer code "
}
]
}
},
{
"record": {
"$": {
"xmlns:ns1": "urn:schemas-qad-com:xml-services"
},
"ns1:ttRBankTransaction_ID": [
{
"_": "47a9-885a-4ec1"
}
],
"ns1:ttRCardknoxTransaction_ID": [
{
"_": "455199587"
}
],
"ns1:ttRBankStateLineNumber": [
{
"_": "1"
}
],
"ns1:tt_result": [
{
"_": "Error"
}
],
"ns1:tt_message": [
{
"_": " Invalid Customer code "
}
]
}
},
{
"record": {
"$": {
"xmlns:ns1": "urn:schemas-qad-com:xml-services"
},
"ns1:ttRBankTransaction_ID": [
{
"_": "47a9-885a-4ec1"
}
],
"ns1:ttRCardknoxTransaction_ID": [
{
"_": "455228164"
}
],
"ns1:ttRBankStateLineNumber": [
{
"_": "2"
}
],
"ns1:tt_result": [
{
"_": "Error"
}
],
"ns1:tt_message": [
{
"_": " Invalid Customer code "
}
]
}
},
{
"record": {
"$": {
"xmlns:ns1": "urn:schemas-qad-com:xml-services"
},
"ns1:ttRBankTransaction_ID": [
{
"_": "82b6-7548-4b81"
}
],
"ns1:ttRCardknoxTransaction_ID": [
{
"_": "474290620"
}
],
"ns1:ttRBankStateLineNumber": [
{
"_": "1"
}
],
"ns1:tt_result": [
{
"_": "Error"
}
],
"ns1:tt_message": [
{
"_": " Invalid Customer code , Invalid Invoice Number"
}
]
}
},
{
"record": {
"$": {
"xmlns:ns1": "urn:schemas-qad-com:xml-services"
},
"ns1:ttRBankTransaction_ID": [
{
"_": "65a8-aa2b-4ea6"
}
],
"ns1:ttRCardknoxTransaction_ID": [
{
"_": "474773339"
}
],
"ns1:ttRBankStateLineNumber": [
{
"_": "1"
}
],
"ns1:tt_result": [
{
"_": "Error"
}
],
"ns1:tt_message": [
{
"_": " Invalid Customer code "
}
]
}
},
{
"record": {
"$": {
"xmlns:ns1": "urn:schemas-qad-com:xml-services"
},
"ns1:ttRBankTransaction_ID": [
{
"_": "650c-494d-40b3"
}
],
"ns1:ttRCardknoxTransaction_ID": [
{
"_": "477425723"
}
],
"ns1:ttRBankStateLineNumber": [
{
"_": "1"
}
],
"ns1:tt_result": [
{
"_": "Error"
}
],
"ns1:tt_message": [
{
"_": " Invalid Customer code "
}
]
}
},
{
"record": {
"$": {
"xmlns:ns1": "urn:schemas-qad-com:xml-services"
},
"ns1:ttRBankTransaction_ID": [
{
"_": "84ba-977f-4ac6"
}
],
"ns1:ttRCardknoxTransaction_ID": [
{
"_": "477914008"
}
],
"ns1:ttRBankStateLineNumber": [
{
"_": "1"
}
],
"ns1:tt_result": [
{
"_": "Error"
}
],
"ns1:tt_message": [
{
"_": " Invalid Customer code "
}
]
}
}
]
}
************************************************************
Export Configuration
**************************************************************
I was expecting to split the record page wise and send it to step 4 one by one.
Please suggest.
Thanks
Sachin - did you give the One-to-Many (Advanced) a try? Then set the 'Path to many' form box to the array with multiple records?
Thanks Courteny & Andrew.
It helped and I can split multiple records and send one by one, downstream with this options.
which field u have provided in one to many where u provided in which step 3 or 4 can u please eloberate im using it for my flow it is very urgent
Hi @kumarmouthiktumuluri,
Could you provide additional information about your workflow? It would be helpful if you could share a screenshot of your Flow Builder setup, including details on your export settings, the preview you're encountering, and the outcomes during the lookup and flow execution compared to your expectations. Providing this information will enable us to better comprehend the context and offer a suitable solution. Please ensure any personally identifiable information is concealed before sharing.
Thank you!