We have set up a Data Source that utilises the Microsoft Office Groups connector and are then trying to connect that Data Source to a Data Lookup form control in a Workflow Form. We appear to have made all those connections, but when we select that Data Lookup, we only get around 100 of the 2000 or so entries that are in the Group?
Is this a limitation of the Data Lookup form control? Is it a limitation of the Microsoft Office Groups connector? Is it something we've done incorrectly in our Microsoft Office Group?
Any pointers on how to get the full list to appear in the Form control would be much appreciated.
By default the REST API implemented behind the connector "Microsoft Office Groups" does not manage paging and the Graph API called limits by default the result to 100 items giving a link to next paging if there more results as described from the Microsoft article : List members - Microsoft Graph v1.0 | Microsoft Docs.
Another option is to extend with Nintex Xtensions by implementing and hosting your payload web API (middleware) that makes all API calls to get all paging results and returns it based on a limit you can also passed in parameter.
By default the REST API implemented behind the connector "Microsoft Office Groups" does not manage paging and the Graph API called limits by default the result to 100 items giving a link to next paging if there more results as described from the Microsoft article : List members - Microsoft Graph v1.0 | Microsoft Docs.
Another option is to extend with Nintex Xtensions by implementing and hosting your payload web API (middleware) that makes all API calls to get all paging results and returns it based on a limit you can also passed in parameter.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
