RELATED IDEAS
Add support for paginated responses from Connector calls such as BOX.ccom
The current connectors for Box.com (and I assume others) do not support pagination. In the case of Box.com when a response has more than 200 items (For example a collection of files in a folder with '201 files') the Nintex connector will only return the first 200 entries.
This can cause logic failures in Workflows that are completing any type of search where the WF must loop through a collection of files or folders. With the current structure, the loop does not find a match if the file that would have been matched is past the first 200 entries.
This can cause logic failures in Workflows that are completing any type of search where the WF must loop through a collection of files or folders. With the current structure, the loop does not find a match if the file that would have been matched is past the first 200 entries.
-
ADMIN RESPONSESep 7, 2022Thanks for the idea for which we've already logged in our backlog.
Currently we have other near term priorities however we re-evaluate requests every quarter and will reach out if priorities change.
-
GuestSep 7, 2022This is a huge issue for using these actions. Please consider fixing this. A quick solution is that the Box API does allow pagination up to 1000. Set that as the default for the action, and then its only a problem for folders over 1000 items. Hence much less of a problem, although still would need a deeper fix.0 reply Hide replies
