Forum Discussion
Microsoft EmployeeShare your thoughts on Automatic Page Refresh aka APR (Preview feature)
As far as I can tell, the change detection measure query doesn't respect RLS. Is this by design?
Adding RLS support will prevent unnecessary queries & renderings for many use cases.
Perhaps the best thing to do will be to add this as an option since there might be situations where ignoring RLS is the right thing to do.
Microsoft EmployeeHi OmriA , thanks for reaching out. When you say RLS you mean the one in DQ source? It should respect that when the data is queried but the chnage detection measure always uses the authors creds to calculate and detect. So yes, there might be situations where the measure changes but the visuals for specific user don't. That is by design because of several reasons. Is this the RLS you talk about or did I miss that completely?
I meant RLS implemented in Power BI using roles.
For example:
I have a table in an SQL server DB. The table has 2 columns [User] & [Score] and the following data tuples:
("User1", 10),
("User2", 20),
("User3", 30)I'm connecting to this table using DQ without any manipulations.
I have a role, implemented in Power BI Desktop, with the following DAX filter on the table: MyTable[User] = "User1".
My change detection measure is MAX(MyTable[Score]).
If I'm viewing the model under the role, I expect the change detection measure to fold the query:
select max([Score])
from MyTable
where [User] = 'User1'Instead, I see that the quey being folded lack the predicate:
select max([Score])
from MyTableSo, if I'll update User1's grade from 10 to 25, the change detection measure will return the same result, 30, and the page will not be refreshed.
Obviously, I can circumstance this in various ways like using CONCATENATEX in my change detection measure, creating a last change timestamp in the source (if I have permissions), etc...
But I think that the change detection query should respect roles implemented in Power BI.