How to get delta data in REST API export
Hi,
Iam trying to process delta data during export in REST API call. How can I can I achieve it?
My EndPoint URL supports a parameter to fetch records that are created or updated after particular time.
Relative URI*: /course?q=(updated_on%3Dge%3D2020-09-11 01:00:00 AM)
Thankz in Advance,
Kiruba Devarajan
0
Comments
Hi,
Iam able to run the delta data with following URL construct in Relative URI field.
It works and thankz for your suppport.
Warm Regards,
Kiruba Devarajan
Hi Kiruba Devarajan,
Could you try this?
Put this in the Relative URI field. As the name suggests, “lastExportDateTime” tracks the last time the export ran. Delta date format is YYYY-MM-DD hh:mm:ss.
Please let us know if that worked!
Hi,
Thankz for quick response. It didn't work. When I use "{{" in handlebar template, I don't get the value "lastExportDateTime" listed in dropdown. Also autopreview doesn't show any value for it.
Iam getting following error when I click "Preview" button on "Edit export" page by changing "Relative URI *" field to "/course?q=(updated_on ge {{lastExportDateTime}})".
Thankz in Advance.
Thanks for letting us know, Kiruba Devarajan! We're still looking for an answer on this for you.
Hi Kiruba Devarajan,
I just checked with our experts and this should work. The problem could be with:
Can you try debugging your connection to see what integrator.io is sending? Thanks!
Hi Kiruba Devarajan,
Please use this format - note the {{{ rather than the {{ is necessary:
This triple {{{ is how you tell handlebars to NOT url/html encode the value returned. The date/time values typically contain ':' chars. Handlebars will encode these chars because handlebars was built to be more generic than just URL params. However, there are times where ':' needs to be url/html encoded, but URLs do not require ':' be encoded in query params. Some APIs that receive our requests will be smart enough to handle either ':' or '%3A' as the url param values, but some might not.
Our adaptors/connectors will automatically encode all the necessary chars in the 'Relative URI' field before sending API requests, so you do not need to worry about encoding URI values themselves.
That said, if you do prefer to encode them yourself, then our adaptors/connectors are also smart enough to ignore/respect '%' chars. i.e. we won't double encode anything.
We did identify an issue during this testing wherein the export panel does not show you that this we are automatically encoding special chars in the URLs. We will get this fixed asap.
Hi,
Thank you. But same issue. Attached the screenshot for reference.
After running the flow.
Thankyou in Advance,
Kiruba Devarajan
Hi,
Please find the debug.
2020-10-17T05:50:55.515Z cf5cc272def243428c47c2de33188a8a export 5f733c223da82c1aa5b39341
{"url":"https://newhorizonssb-api.sabacloud.com/v1/course?q=(updated_on ge )","method":"GET","headers":{"accept":"application/json","user":"S••••••••1","password":"P•••••••••••0!","content-type":"application/json","SabaCertificate":"********"}}
Last run date time value is not present in url.
Thankz in advance,
Kiruba Devarajan
Hi Kiruba Devarajan,
We tested the solution and it should have worked. Could you enter a support ticket on this so that we can get this resolved more quickly for you? Thanks!
Hi,
Thankyou. Will do so.
That is great to hear, Kiruba Devarajan! Thank you so much for letting us know! I've marked yours as the accepted answer.
Please sign in to leave a comment.