Download tool does not download $skiptoken

[Teet_Rannut]

The case is described in detail in the attached pdf.

Hope someone has already solved such issue and can teach me.

[apathetichell]

That should be a json key/value in Download Data. Post what API you are hitting -> not your companies host -> the ERP you are using - is it Dynamics or an SAP thing? If you do not see the token in download data - you will need to post the API specs.

[Teet_Rannut]

It is on OnPrem Dynamics Business Central. Please let me know what API specs should I post here - I shall ask the ERP support team for the specs then.

[apathetichell]

check out your full download data field -> which you should be sending to your output data. Your odata info should be additional json fields there. In your json parse -> it looks like you are using value to parse your values. You should see context and the other as additional json keys to parse.

[Teet_Rannut]

Yes, this is the problem - I checked the full andmed.json that I wrote down directly from download tool output, also seen in my workflow. I pulled the json into notepad++ and could find neither "next*" nor "skiptoken*" in it. The first and last part of the json can be seen in my original pdf that I posted when I opened this case, please look at "Response in Alteryx, first rows, last rows:".

The parsing and filter tool are in my workflow example only because this is part of workflow that works beautifully against cloud Dynamics API of another company I am supporting.

Please let me know if there is more I should check or do, I am grateful of all hints.

[apathetichell · Accepted solution]

the odata information should be additional key/values in your download data. can you attach a screenshot of the config of your json parse tool? -> can you also filter for the last rows of data after your json parse tool? - figure the last 10 records? what are the json keys (names) there -> please post that with any key secure information removed.

[Teet_Rannut]

Thanks for crucial hint that solved my problem!

I was too careful, because I had to test my workflow against production environment, so I cut the period for records to be retrieved very short (and made my tests preferably after business hours).

I discovered that $filter=postingDate gt 2025-01-01 and postingDate lt 2025-01-03 when sent from download tool retrieved less than 5300 records, so no next.Link was created. When I changed it to lt 2025-01-09 I got next:Link with $skiptoken value in the filter tool in my workflow. 

Actually there were over 20 000 records on that day that Postman retrieved. It is an old bug/feature in the download tool or server communication (but works fine with Postman) - for some reason occasionally part of the records are lost from the first or last day of the filtered period. Luckily that has a straightforward workaround I have been using for a long time already - I retrieve longer period and filter out the surplus days' records.

Thanks again!

[apathetichell]

Awesome! Glad this worked out -> I figured that it would be somewhere in the odata payload.