Power BI Report Builder Dataverse Permissions

Thankyou, mh2587, for your response.

Hi lherbert501,

Based on our understanding, the behavior may be expected when the Dataverse data source is configured with OAuth2 and the option Report viewers can access this data source with their own Power BI identities is enabled. In this setup, the paginated report uses each viewer's own Microsoft Entra ID (SSO) identity to access Dataverse instead of stored credentials. This might be the reason why the username and password fields are greyed out and cannot be edited manually.

Since the report works for you but fails for another user, the issue may be related to the affected user's Dataverse environment access, Dataverse security roles or table permissions, or Power BI workspace, report, and dataset permissions.

Please verify whether the user exists in the Dataverse environment, has appropriate security roles with read access to the tables or entities used in the report, and the user has access to the Power BI report or workspace.
Additionally, ask the user to sign out and sign back into Power BI, or test using an InPrivate or Incognito browser session to refresh OAuth tokens.

Please find the links below for reference:
Supported Data Sources for Power BI Paginated Reports - Power BI | Microsoft Learn
Role-based security roles for Dataverse - Power Platform | Microsoft Learn

We hope the information provided helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.