Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Carl_Hunter
Partner Ambassador
Partner Ambassador

How to handle pagination in a Call URL block?

I'm pulling data from MS Graph, which provides its data in an OData format. I am only getting the first 100 records when doing a GET request via a Call URL block. 

MS Graph handles pagination by providing a Next Link attribute in the header of the GET response - see below in Yellow. I've tried grabbing that url and putting into another Call URL block but it doesnt seem to work. 

Carl_Hunter_0-1641570650878.png

How do I handle pagination when using Call URL via a GET request?

Labels (2)
1 Solution

Accepted Solutions
gkj
Employee
Employee

Hi @Carl_Hunter 

The call URL block does not support pagination, but you can construct the next page manually via e.g. the next page URL specifically here by using OData next link

I have created automation where the pagination is done for this specific use case(cursor type paging) and it will list out all items using call URL block.

Sharing the workspace

Hope this helps!!

Thanks!!

Afeefa TK

 

View solution in original post

3 Replies
Carl_Hunter
Partner Ambassador
Partner Ambassador
Author

If I was to pull data from MS Graph from a QLik Sense data load script, I'd use the REST connector, and specify Pagination type as "Next URL" and set the location of the next url within the json response i.e. root/@odata.nextLink - see below.

I dont see this option in Automations nor a way to do it? 

Carl_Hunter_0-1641578812295.png

Here is the json response showing the next url link

Carl_Hunter_1-1641578992124.png

 

 

gkj
Employee
Employee

Hi @Carl_Hunter 
Thanks for reaching out

Could you please try using this formula { $.callURL.body.['@odata.nextLink'] } as URL in the call URL block  and see if that works

Best Regards!!

Afeefa TK

gkj
Employee
Employee

Hi @Carl_Hunter 

The call URL block does not support pagination, but you can construct the next page manually via e.g. the next page URL specifically here by using OData next link

I have created automation where the pagination is done for this specific use case(cursor type paging) and it will list out all items using call URL block.

Sharing the workspace

Hope this helps!!

Thanks!!

Afeefa TK