+3Hello all!
I'm trying to use the Box action: "Get Folder Contents."
Is this limitation documented somewhere? Is there a way to interate through to get them all (possibly by buiding mutiple collections)?
Thank you.
Best answer by butlerj
@mikeboggs23 this looks like it's an issue on the NWC action side where it does not paginate the response from the box folder. There is an open feature request for this (https://nintex.uservoice.com/forums/430063-5-nintex-workflow-cloud/suggestions/40062262-add-support-for-paginated-responses-from-connector) and the development team is aware of the issue and investigating potential solutions/workarounds.
+20@mikeboggs23 I'm seeing the same thing when I test. Doing some additional investigation to understand if this is an API limitation on the Box API that we're calling, or if this is something that we need to update on our side.
Will update when I know more.
+20@mikeboggs23 this looks like it's an issue on the NWC action side where it does not paginate the response from the box folder. There is an open feature request for this (https://nintex.uservoice.com/forums/430063-5-nintex-workflow-cloud/suggestions/40062262-add-support-for-paginated-responses-from-connector) and the development team is aware of the issue and investigating potential solutions/workarounds.
+3Thank you. I'll add my votes to that request.
That being said, the actual Box API allows for each page to go up to 1000. I'm assuming it defaults to 200. So without having to support full pagination, you could easly up the return to 1000 and solve at least some peoples issues. https://developer.box.com/reference/get-folders-id-items/
That might be a quick win, while they work on full pagination support.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
