Hi Expert,
Can we use a POST integration API which actually queries data from a third party system to configure as a Sync Record Data Source, if yes then how ?I have created an expression to get the data using the integration object which is working fine in the Expression rule while throwing error on using the same in Record Type.
Thanks,
Gaurav Singh
Discussion posts and replies are publicly visible
GauravSingh said:while throwing error on using the same in Record Type
What was the error you are getting?
GauravSingh said:Can we use a POST integration API which actually queries data from a third party system to configure as a Sync Record Data Source, if yes then how ?
https://docs.appian.com/suite/help/24.1/configure-record-data-source.html#prodlink-web-service this might help, Please go through it and keep it mind You can only sync 1000 records at a go that too when the query don't take to much time so design you sync calls to avoid timeout
Yes, simply create a Web API with a POST method that calls a Process Model which does the POST request to retrieve the data.
Than you can create an Integration which calls your API with the POST method but with "Queries Data" instead of "Modifiies Data" and set it as your Record Data Source.
Hi Mathieu,
I have already created the integration object using the connection details and API provided by the third party application team.
Now when I'm trying to configure it as source for the recordType I'm not able to do so.
What error do you get?
Could you share what your recordDataSource is returning by any chance?
Do you want me to help you or not?
Can you show the contents of the dictionary?
I wish to share the complete details but will make me to find another Job Lolz..
This is how it looks like but contains more attributes.
{ profiles: { { id: "some value", uid: "uid", name: "test", profile_type_id: "some value", status: "Active", id_proofing_status: "pending", updated_at: fn!datetime(2024, 10, 14, 17, 43, 37, 40), created_at: fn!datetime(2022, 5, 17, 0, 36, 59, 0), attributes: { security_id: "", confirm_start_of_audit_ne_attribute: "Yes", personal_last_name: "Bourne", . . . few more attributes . . . } }, { id: "some value", uid: "uid", name: "test", profile_type_id: "some value", status: "Active", id_proofing_status: "pending", updated_at: fn!datetime(2024, 10, 14, 17, 43, 37, 40), created_at: fn!datetime(2022, 5, 17, 0, 36, 59, 0), attributes: { security_id: "", confirm_start_of_audit_ne_attribute: "Yes", personal_last_name: "Chase" . . . few more attributes . . . } } } }
I have a feeling it's just because you have to drill down in the nesting. Service Backed Record type structures don't support nested attributes, your data structure need to be flat.
Source Data:
Record Data Source:
Record Type: