cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Syndicate_Admin
Administrator
Administrator

Enable pagination for Custom Connector Action

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.

1 ACCEPTED SOLUTION

Accepted Solutions
Syndicate_Admin
Administrator
Administrator

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 👍.

View solution in original post

5 REPLIES 5
Syndicate_Admin
Administrator
Administrator

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 👍.

 

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'. '



 

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}

AdamTheNagy_0-1626336999041.png

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

AdamTheNagy_1-1626337038348.png

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

 

Any ideas?



Syndicate_Admin
Administrator
Administrator

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 👍.

View solution in original post

That's sad, but thanks for the confirmation!

Helpful resources

Announcements
PA_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

Power Query PA Forum 768x460.png

Check it out!

Did you know that you can visit the Power Query Forum in Power BI and now Power Apps

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

PowerPlatform 768x460.png

Microsoft Learn

Check out our new Discover Your Career Path blog post series and get all the details.

Top Solution Authors
Users online (2,075)