Skip to main content
Solved

Pagination for REST API Azure active directory


Hi,

I'd like to make a new data source connection using REST to connect with our Azure storage table.

Thus far I have managed to get the connection setup, however pagination remains a issue.

When testing our connection and following the steps in the debug logging file I see that when a table has a next: "x-ms-continuation-NextPartitionKey” and "x-ms-continuation-NextRowKey” it will return this in the header (not the body). But if the table doesn't have this it will stop since the "x-ms-continuation-NextPartitionKey” header was not found.

As I am applying these pagination parameters as query parameter I need to be able to solve this issue.

Is there maybe a way to apply a default value to these variables (manipulating query doesn't work as the variable itself already won't be found) or some way to dynamically replace a URL? 

Example table with no NextPartition/rowkey:

When variable value replaced with default:

Thanks for any input someone can provide.

Kind regards,

Robbert

Best answer by Robbert_T

Hi sorry for the late reply,

Managed to get it working, partly my own fault for not fully understanding how API's work (new to this subject) and how to translate it in the portal.

How it's solved now is with this configuration in the endpoint.

$filter is a query parameter on endpoint with the %20 replaced with a space.

Going for a custom URL replacement was the way to go for this. 

Thanks for the quick responses, I did have a look at the tutorials and it did help me understand things better.

Kind regards,

Robbert

View original
Did this topic help you find an answer to your question?

4 replies

anders.e.jonsson
Contributor
Forum|alt.badge.img+1

Hi ​@Robbert_T 

I’m not quite sure I understand your problem. But, you say that you the header wasn’t found. Have you tried “Override Headers” in the main settings or the endpoint settings. Maybe you could supply the header and a proper value there.
Or “Pagination” , and check the box “Replace URL”.

BR
Anders


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • 1094 replies
  • June 3, 2025

Hi ​@Robbert_T 

I use the for connecting to Azure Active Directory.

There likely is some similarities in behavior for this. For example how pagination is done. This is only possible if the amount of rows is above the default $top parameter value.

Regarding header based pagination, my GoREST guide explains how you can do this.

 


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@Robbert_T  does Thomas’ answer above resolve your issue? If so please help us by marking the comment as best answer. Please let us know if you have any follow up questions


  • Author
  • Starter
  • 1 reply
  • Answer
  • June 16, 2025

Hi sorry for the late reply,

Managed to get it working, partly my own fault for not fully understanding how API's work (new to this subject) and how to translate it in the portal.

How it's solved now is with this configuration in the endpoint.

$filter is a query parameter on endpoint with the %20 replaced with a space.

Going for a custom URL replacement was the way to go for this. 

Thanks for the quick responses, I did have a look at the tutorials and it did help me understand things better.

Kind regards,

Robbert


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings