Power BI icon

Power BI

Work with the Power BI API

Overview

This node interacts with the Power BI API to retrieve information about users associated with a specific datasource within a gateway. It is useful in scenarios where you need to manage or audit user access to data sources in Power BI gateways, such as verifying who has permissions on a datasource or integrating user data into workflows for reporting or compliance.

For example, you might use this node to:

  • Automatically fetch and list all users who have access to a particular datasource in a gateway.
  • Trigger notifications or audits based on datasource user changes.
  • Integrate datasource user information into broader business intelligence or security workflows.

Properties

Name Meaning
Authentication Method of authentication to use:
- OAuth2
- Bearer Token
Gateway Name or ID The gateway that contains the datasource. You can select from a list of available gateways or specify an ID using an expression. This identifies the gateway context for the datasource.
Datasource Name or ID The datasource within the selected gateway to get users for. You can select from a list or specify an ID using an expression.

Output

The node outputs JSON data containing the list of users associated with the specified datasource in the gateway. Each item in the output array represents a user with their relevant details as returned by the Power BI API.

If the node supports binary data output (not indicated here), it would typically represent files or attachments related to the datasource users, but this node primarily outputs JSON user data.

Dependencies

  • Requires valid authentication credentials for the Power BI API, either via OAuth2 or a bearer token.
  • Needs access to the Power BI service with sufficient permissions to query gateway and datasource user information.
  • The node depends on dynamic loading methods to populate selectable options for gateways and datasources (getGateways and getDatasources), which require proper API connectivity.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens will cause authorization errors.
    • Specifying a gateway or datasource ID that does not exist or to which the authenticated user lacks access will result in errors.
    • Network or API rate limiting issues may cause request failures.
  • Error Messages:

    • "The resource "gateway" is not supported!" — indicates an unsupported resource was selected; ensure the correct resource and operation are chosen.
    • Authorization errors typically mention invalid credentials or insufficient permissions; verify your API key or OAuth2 token and permissions.
    • Errors related to loading options (gateways/datasources) suggest connectivity or permission problems.
  • Resolutions:

    • Refresh or reauthenticate your credentials.
    • Confirm that the gateway and datasource IDs are correct and accessible.
    • Check network connectivity and API limits.

Links and References

Discussion