Cross data in power bi services

[Anonymous]

Good evening dear,

I am having a serious problem at the company I work for. We create a sales report which is fed from a SQL database, and we publish it in power bi service in an application created in the power bi service. We have 20 different clients, and the problem is that when we log in with user X (of a client) and then in an incognito window we log in with user Y (of another client), we see that the user's data And they are not correct, and at the same time the data of user X is observed in the Y. Let's say that the data is crossed. At the same time, when we update the report in the application, data is changed again. There are times when waiting a time of 10 minutes, everything is restored and the data is observed perfectly, but it may be that after a few minutes, the customer data is crossed again.

Please could you give me an idea of ​​what is happening? is it database issue? or is it a power bi service issue?

Regards.

[lbendlin]

How do you separate client X from client Y - do you use Row Level Security on the dataset?

[Anonymous]

That client X is separated from Y by a statement in sql, in the database, each user has an assigned ID. Does not use RLS security

[lbendlin]

I don't think that is a viable or secure setup.  Have a hard look at potential browser cache issues, potential Content Delivery Provider issues  and potential query caching on your source.

[Anonymous]

I explain a little more the subject.
It has happened to us that being logged in with a user X in PowerBI, PowerBI Gateway sends the information to the SQL Server as if user Y were connecting.
Although it is working, it happens that when at the same time there is more than one user connected, we find that:

1) the PowerBI Gateway service no longer respects the user issuing the query
2) or, the PowerBI service is sending the information in the wrong way to PowerBI Gateway

PLEASE, ANY OPINION ABOUT IT?

[lbendlin]

1) is standard operating procedure for the gateway. You need to change your setup if you want it to behave differently.

[Anonymous]

To the commented:
1) is a standard operating procedure for the gateway. You need to change its settings if you want it to behave differently.
What would those configurations you tell me about? Could you help me with a list of the configurations that you indicated?
Other things, no less, we are using RLS at the database level, and this way of working is what brings us problems.

Regards.

[lbendlin]

For Direct Query connections you can configure credential pass-through.