Do not apply security on a visual object

[pasqualino]

Hello,

I am just learning PowerBI, so I beg you pardon for what I can write.

I have a dashboard with multiple visualizations, being most of them filtered on a Table based roles (Users will only see lines whose column X has a certain value), that works fine.

On the other side, I need one calculation that should consider all the values, not only the X ones.

I though about duplicating the table where the role is applied and calculate visualization on that.

Is that reasonable?

[v-nmadadi-msft · Accepted solution]

Hi @pasqualino,
Thanks for reaching out to the Microsoft fabric community forum.

You cannot disable Row-Level Security (RLS) for a specific visual while still using the same table, as RLS is applied at the dataset level and affects all visuals connected to that dataset. Additionally, you cannot bypass RLS using DAX as well.
So to bypass the limitation
we have to achieve selective application of Row-Level Security (RLS), you can duplicate or summarize your data into a new table that excludes any sensitive or personally identifiable information (PII).
This new table should not be included in any RLS role definitions. You can then use this non-RLS table specifically for the visual that needs to be exempt from RLS, while continuing to use the original RLS-protected table for all other visuals.
 This ensures that RLS is only applied to the visuals connected to the secured table, allowing the designated visual to remain visible to all users without restriction.

If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards

[pasqualino]

thanks for all that supported, I had a personal constraint and could not reply earlier. 

[v-nmadadi-msft · Accepted solution]

Hi @pasqualino ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the community members for the issue worked. If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Thanks and regards

[v-nmadadi-msft]

Hi @pasqualino,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If our responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-nmadadi-msft]

Hi @pasqualino ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-nmadadi-msft · Accepted solution]

Hi @pasqualino,
Thanks for reaching out to the Microsoft fabric community forum.

You cannot disable Row-Level Security (RLS) for a specific visual while still using the same table, as RLS is applied at the dataset level and affects all visuals connected to that dataset. Additionally, you cannot bypass RLS using DAX as well.
So to bypass the limitation
we have to achieve selective application of Row-Level Security (RLS), you can duplicate or summarize your data into a new table that excludes any sensitive or personally identifiable information (PII).
This new table should not be included in any RLS role definitions. You can then use this non-RLS table specifically for the visual that needs to be exempt from RLS, while continuing to use the original RLS-protected table for all other visuals.
 This ensures that RLS is only applied to the visuals connected to the secured table, allowing the designated visual to remain visible to all users without restriction.

If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards

[lbendlin]

Yes, a hidden aggregated table without PII and without RLS is reasonable.