Add a way to specify a SharePoint list by name in the Microsoft SharePoint Online REST connector, rather than only picking from the list dropdown. Hidden lists never appear in the dropdown, so they cannot be selected at all today — a regular requirement to enable the resolving of People names is the "User Information List" which is site specific.
Two acceptable shapes:
1. A "Custom List Name" / "List Title" free-text field on the List Items report, so any list can be named directly (including hidden system lists).
2. A dedicated report that reads the site's User Information List, scoped to the site you point at.
Use case
SharePoint lists use People & Groups columns heavily — created-by, assigned-to, approver, owner. The connector returns the user details for some of these standard fields, but when a "people picker" is added to a list, they're returned only as a bare integer lookup ID. The values that resolve those IDs live in the site's User Information List (/_catalogs/users), which is hidden, so there is no way to pull it through the connector and join on it. The dataset arrives with unusable ID columns and the only fix is outside Domo.
The existing "Users" report is not a substitute: it is not scoped to a site, so it does not return the per-site lookup IDs the list items reference.
Current workarounds:
- Have SharePoint admins export the user list manually and upload it as a flat file, which goes stale immediately.
- Build a JSON No Code or fully custom connector against /_api/web/lists/getbytitle('User Information List')/items — duplicating a connector that already exists, and adding a second account and credential to govern.
- Utilise Power Automate to export the User Information List to a CSV file on SharePoint and ingest file into Domo
The first 2 options are quite poor, and I'm currently using the last option which does provide some flexibility.
The Power Automate option actually works well, providing the user information list is only required to be updated at fairly generic intervals. However, it creates other limitations as only certain people are able to set this up (Requires Power Automate license, best to use generic/service account; so credentials are not shareable), more advanced scheduling is difficult and unreliable.