Forum Discussion

Bhavik13101991's avatar
Bhavik13101991
New Member
1 day ago

Power BI Embedded: Multiple Users Seeing the Last Logged-In District's Data

Hi,

We have a Power BI report embedded in our .NET application. We use DirectQuery, and our SQL Server production environment contains around 1,800 databases. In Power BI, we pass a database parameter to connect the report to the appropriate district's database.

Each user belongs to a specific district, and the report should display data only from their respective district/database.

We are facing an issue when multiple users log in at the same time.

For example, User A logs in from District A, and the report connects to the District A database and displays the correct data.

Then User B logs in from District B, and the report connects to the District B database.

After User B logs in, User A also starts seeing District B data.

It appears that the last-loaded database parameter value is being used by all users instead of maintaining a separate database parameter value for each user's embedded report session.

We are using Power BI Embedded with a .NET application and DirectQuery, with approximately 1,800 SQL databases in production.

What is the recommended approach for this scenario? How can we ensure that each user's embedded Power BI report independently uses the correct database parameter without affecting other users?

Would Dynamic RLS, effective identity, separate embed tokens, or another Power BI Embedded approach be appropriate for this architecture?

Any guidance on how Power BI handles parameters and DirectQuery connections for multiple concurrent embedded users would be greatly appreciated.

Thanks!

2 Replies

  • We also use an on-premises data gateway. The gateway data source connection is updated dynamically using the Power BI Update Datasource REST API. Based on the server and database values, we update the corresponding database parameter in the Power BI report.