I’ve tried all the right things:
- Created, deployed, and configured custom connector into the target environment before importing the solution that uses the connector. All tests pass.
- Created a manual Power Automate flow as part of the solution.
- Shared the flow with the user (should not need to for the solution flows but just in case)
- Ensured that the flow runtime permissions are set correctly (correct use of run-only permissions)
- Shared custom connector with the user (should not need to but just in case)
And yet, when the said user tried to run the flow they kept getting this error message
This information seems to be helpful but then it generates more questions than answers:
- Operation on entity with id XXX. Is that a record with that id or id of the actual entity/table?
- What entity/table are we talking about here?
- The flow uses unspecified list of apps – what is the relevance of this?
Long story short: user was missing read privileges on Connector table (and id mentioned is the id of the entity/table not of the record in the table). There are two Connector tables on the most instances I’ve seen and, just like the USB, you are going to get the first one wrong. There is an easier solution to the problem: assign Basic User role to the user. One of the permissions it includes is that very permission to read custom connectors (what did you think is in the Connector table?!).
Cover image by ds_30