Enable pagination for Custom Connector Action

[AdamTheNagy]

How can I enable pagination for an Action in my Custom Connector?
I can see here that it can be enabled for some components:
https://flow.microsoft.com/en-us/blog/four-connector-action-settings/ 

I follow the OpenAPI x-pagination / cursor option shown here https://www.transposit.com/blog/2019.12.10-using-extensions-to-support-pagination-in-openapi/ to add it to my connector, but the Pagination option in the Settings does not show up. 

I did not find any info that about this.

[murshed]

The x-ms-pageable may be helpful. Here is an example connector.

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.

[AdamTheNagy]

Thank you for the reply! 
However, I wonder if it's more Azure specific and not for Connectors in general? - e.g. it's not listed here https://docs.microsoft.com/en-us/connectors/custom-connectors/openapi-extensions and what it accepts is pretty limited. When I try to use it with the response body I get where the info is inside pagination->nextUrl, I get this error:

Specified swagger has the following errors: 'Definition is not valid. Error: 'Error : paths/~1exchange~1v1~1collections~1{collectionId}~1spaces~1{containerId}~1sync/get/x-ms-pageable/nextLinkName : The nextLinkName value for operation 'GetData' is invalid. Supported values are 'nextLink' or '@odata.nextLink'. '

[AdamTheNagy]

Update: adding this to the swagger definition of the Custom Connector does add the Pagination option to the Settings dialog:

x-ms-pageable: {nextLinkName: nextLink}

But it will not work, because it expects a certain type of content in the response body:

Not sure if it can be made to work with a different response body.

Any ideas?

[murshed · Accepted solution]

Sorry that you are having trouble with this feature. The API will need to implement @odata.nextLink.

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.

[AdamTheNagy]

That's sad, but thanks for the confirmation!

[NicoleMyM]

Hi, your response needs 'value'

But, I have another error after that.

[NicoleMyM]

Hi murshed.

I'm trying to implement nextlink in a custom connector in Power Automate.

My custom connector has pagination active.

API response the nextlink

The flow show this error.

Outputs

What could be wrong or missing? 

I would appreciate your help 🙂

[NickTLS]

Were you able to figure this out without having to edit the API body response? I am trying to build a custom connector to an API that doesn’t return a nextLink value.