Forum Discussion
Data Source issues in Power BI Service
Hello,
We currently use On-Prem Server and reports display correctly. Most of the reports are Paginated reports.
We have a DB that have 2 user accounts
Account A:
User name: Johnb
Password: Jex
Account B:
Username: Fox
Password: Fox2b.
The credentials pulls correct data in report Server.
I created 2 work spaces for Project A and B in service. Reports A goes to workspace A and reports B goes to workspace B.
When I run reports A, it pulls expected data but when I run report B it pulls Report A data but the same file pulls correct data in Report Server or when run it outside the server.
The Gateway was configured with A credentials. Does anyone have idea on how to fix this?
Hi mjsystemss,
You can set up different connections on the gateway for A and B so they remain seperate.
Are the reports intended to be the same just with different data based on the user's access, or are they fully different reports?
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi mjsystemss , Thank you for reaching out to the Microsoft Community Forum.
tayloramy is correct, the issue really does come down to how the on-premises data gateway is configured. Because the gateway was set up with Account A’s credentials, every report that uses that gateway will connect to the database as Account A, even those published to Workspace B. That’s why Report B is showing Report A’s data in the Power BI Service even though it works correctly on-prem or locally.
Create separate gateway data sources, one for each database account and make sure each workspace or paginated report is mapped to the right one. In Power BI Service, open Manage Connections and Gateways, add a new data source for the same database but use Account B’s credentials and assign Workspace B’s reports to it. Workspace A can keep using the existing data source tied to Account A. Once each workspace is mapped to the correct gateway data source, the reports will pull the expected data.
Manage an on-premises data gateway | Microsoft Learn
Add or remove a gateway data source - Power BI | Microsoft Learn
Supported data sources for Power BI paginated reports - Power BI | Microsoft Learn
Thank you tayloramy for your valuable response.
2 Replies
Hi mjsystemss,
You can set up different connections on the gateway for A and B so they remain seperate.
Are the reports intended to be the same just with different data based on the user's access, or are they fully different reports?
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi mjsystemss , Thank you for reaching out to the Microsoft Community Forum.
tayloramy is correct, the issue really does come down to how the on-premises data gateway is configured. Because the gateway was set up with Account A’s credentials, every report that uses that gateway will connect to the database as Account A, even those published to Workspace B. That’s why Report B is showing Report A’s data in the Power BI Service even though it works correctly on-prem or locally.
Create separate gateway data sources, one for each database account and make sure each workspace or paginated report is mapped to the right one. In Power BI Service, open Manage Connections and Gateways, add a new data source for the same database but use Account B’s credentials and assign Workspace B’s reports to it. Workspace A can keep using the existing data source tied to Account A. Once each workspace is mapped to the correct gateway data source, the reports will pull the expected data.
Manage an on-premises data gateway | Microsoft Learn
Add or remove a gateway data source - Power BI | Microsoft Learn
Supported data sources for Power BI paginated reports - Power BI | Microsoft Learn
Thank you tayloramy for your valuable response.