I have an export in one of the celigo flows in which i am trying to export records from Generic Inquiry in Acumatica. We have set up the Generic Inquiry to pull specific fields from a table (it is kind of database view where we pull all fields we need). But the issue is ‘it is exporting only one record’ and so updating only one record in the destination. I have selected ‘Export all data’ , also tried grouping the records ‘ContractCD’ value (you can find this in screenshot). Still no luck. Any suggestions would be helpful.
Vyshnavi, if I am correct an Acumatica Generic Inquiry response looks something like this
{
"@odata.context": "...",
"value": [
{
"Field1": "Record 1 Value A",
"Field2": "Record 1 Value B",
"Field3": "Record 1 Value C"
},
{
"Field1": "Record 2 Value A",
"Field2": "Record 2 Value B",
"Field3": "Record 2 Value C"
},
// ... continues for all records
]
}
So in order to get Integrator.IO to recognize each record (instead of the array) you will want to set the “Path to records in HTTP response body“ in the export to ‘value‘.
Thank you very much for the reply. Here is what i am getting from Acumatica GI. Do i need to add ‘Tranformation’ step to transform the json..?? Because with this JSON even if i enter ‘rows’ or ‘page_of_records’, it is returning empty response.
ServiceNowID field is the unique field i want to use to differentiate each record. So i have given ‘ServiceNowID.value’ in grouping the records option in export.
Also, Since you mentioned trying to group by ServiceNowID, are you doing that on the Generic Inquiry in Acumatica or via the settings in Integrator.IO?
Can you please try removing the grouping for now until you validate you are getting the correct data.
in your previous example you had a ROWS array. it doesn’t appear to be there in the HTTP response, did you change something else before taking that screenshot? I would have expected the ROWS to still be there.
This may have something to do with the grouping you had. If you are were trying to group by ServiceNowID and there was only one record with that ID then IO would only show the one records in the grouping since that is all that exists.
The preview button will only show a subset of your data, If you actually run the flow you may get all of the expected records.
HTTP response stays the same as shown in the above screenshot without any ROWS array, with or without grouping. I have sent you Parsed Output before which had ‘ROWS’.
I have tried running the flow thinking the same, that preview might be just showing single record. But it did not update multiple records, it only updated the one showing in the preview.
If HTTP response shows like below, with or wothout grouping, are there any other setting i need to do interms of export scenario OR is there anything else i can try with ‘Path to records in HTTP response body’..??? or will i need to transform the JSON to accept multiple records..?? Please assist
Hi, Based on the screenshot of the http response, It looks to me like your API is only returning one record and not multiple. You can verify this in Postman.
For example here is a screenshot of a call to the Acumatica Customers endpoint, the HTTP response shows that Acumatica is returning an json array containing multiple customer objects:
