Unanswered

Custom Connector for Graph API with Pagination

(1) Share

Report

Posted on by matthudson

I've set up a custom connector to interface with Graph API using an azure app. Everything works fine except for trying to enable pagination - from what I've read all you need to add is an x-ms-pageable value via the swagger editor, and it should handle everything automatically. Unfortunately, Power Automate throws an InvalidAuthenticationToken (IDX14100: JWT is not well formed)

whenever it tries to use pagination (disabling it, or returning under 20 records works fine)

Before I go and rewrite everything to use skiptoken as an input (because that'll be a lot of work on the flow end to get all the records I want), has anyone had any luck getting this to work as it should?

Categories:

Using connectors

I have the same question (0)

All responses (10)

Answers (0)

Sort by

__2A 6 on at

Like (1)

Report
Copy link

Link copied!

I have exactly the same problem. Disabling pagination the connector works just fine. And using the "HTTP" action with the pagination option enabled works too.

Was this reply helpful? Yes No
matthudson 17 on at

Like (0)

Report
Copy link

Link copied!

Sorry, no update yet. Ticket opened with Microsoft, will let you know when I have a fix

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report
Copy link

Link copied!
I don't get any error message (querying emea.api.flow.microsoft.com), but pagination isn't happening: Only 50 rows are returned and the nextLink.
All did in the Swagger editor was to add this code bit:

x-ms-pageable: nextLinkName: 'nextLink'

Should this work or am I missing something here?

Was this reply helpful? Yes No
matthudson 17 on at

Like (1)

Report
Copy link

Link copied!

You'll need to enable pagination in the settings for the block in the flow:

I've tested and it's still broken, unfortunately

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report
Copy link

Link copied!

Thanks @matthudson ,
but my question was for a custom connector. Those actions don't show the pagination feature from your screenshot.

Was this reply helpful? Yes No
matthudson 17 on at

Like (1)

Report
Copy link

Link copied!

All you've done is tell your custom connector that it supports pagination; until you enable it on your flow block it'll ignore any nextlink and continue to only return the first page.

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report
Copy link

Link copied!

Thanks @matthudson ,
that was it!
Could swear, this setting wasn't there before - but hey, it was a long day... that you saved at last thankfully 🙂

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report
Copy link

Link copied!

Actually, my excitement was a bit premature.
When enabling "Pagination" in the setting as you have described @matthudson , I am getting 401 "CompactToken parsing failed with error code: 80049217".
Is that what you are seeing as well?

Was this reply helpful? Yes No
matthudson 17 on at

Like (1)

Report
Copy link

Link copied!

Yep, same error here. No luck yet with Microsoft support; I had to put the ticket on hold due to other priorities at work, but when I pick it back up and we get it fixed I'll update the thread

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report
Copy link

Link copied!

Hi @matthudson ,
pagination is working for me now: https://github.com/microsoft/PowerPlatformConnectors/issues/2959#issuecomment-1821632116

Was this reply helpful? Yes No