Odata connection paginated and missing the input for next page

[akarpati]

Hi all,

I was able to create a workflow to retrieve data via an Odata connection from a source system. However the content seems to be paginated to 100 records at once. I have also found a solution in form of an iterative macro how it could be solved, but there seems to be an input needed for this macro from the Odata connection which would lead the macro to find the "next page".

This is my original workflow:

This is working properly, but only for 100 record:

Here is the iteration macro I have found also in the community:

As you can see this iteration macro would need the "result._links.next" in order to continue with the iteration. 

When I have tried to apply this macro to my current workflow (of course replacing the links to my particular one), I have faced the problem that among the DownloadData I got only the odata context, but I don't receive the odata next link, so there is no link for the next "page", what could be the input for the iteration macro. 

Do you have any idea if there could be any settings adjusted in the workflow, or this is rather something that should be handled from the data provider side?

The configuration of my Download tool:

Thanks in advance!

Best regards,

Antal

[apathetichell]

this is all API specific (and ODATA syntax can be also be very specific). Can you share what API you are hitting? My standard suggestion is to see if you can use a COUNT() with your ODATA call to get the total number of records. then you can divide up the total number of records by the limit per call (there's standard limiting in ODATA) and create an API call for each using offest in your ODATA call. I do not use an iterative macro.

More details - for uipath - I look for [JSON_Name] = "@odata.count" which provides the total record count.

I use a formula like if [api_Call]=0 then [URL-TenantSpecific]+[Resource]+"?$top=1000" else [URL-TenantSpecific]+[Resource]+"?$skip="+tostring([api_Call]*1000) endif to create te specific calls.

[akarpati]

Hi,

I guess that's from where my problem is coming - in the JSON Name I can't find any other odata information, only the odata context:

I would expect the odata next link, or the odata count after I am extracting the JSON, but basically everything else is just missing.

Thanks,
Antal

[apathetichell]

If you can share the API/link to the developer resource - I can provide you information. Otherwise despite my tremendous psychic powers - I really can't do too much. You probably need to include a specific argument to get the count. 

[akarpati]

Hello,

so this is my main URL (I have to blur certain details of it): 

This gives me a list of 'tables' I can connect to (under value.x.name) and only one record with @odata.context, nothing else:

Shall I enter the URL differently?

Thanks,

Antal

[Tommy_Alterax]

Hi Guys -I am at the same stage - did you solve this ? 

[apathetichell]

@Tommy_Alterax --- what is the API you are using? as a reminder --- your credentials are your credentials --- they are secret. your endpoints --- those should be secret. The API documentation --- in 99.99% of situations that is public. That is from the SAAS system and that is usually not secret. If you let use know the system is really really helps.