Forum Discussion

raju8004212's avatar
raju8004212
Frequent Visitor
1 year ago
Solved

Dynamic Row level security

Hi Anonymous  dynamic swithcing of rls is  based on slicer selection rls logic working with out selection if we  include slicer selection  in rls its not wrking  my model is like bu_org ,snap co...
Need Help
  • v-sshirivolu's avatar
    v-sshirivolu
    11 months ago

    Hi raju8004212 ,
    To clarify it isn’t possible to pass slicer values or variables into RLS. Power BI always applies     RLS first (based on user identity), and only afterwards slicers/filters.

    That means a “toggle RLS by slicer” design isn’t supported. The only supported approaches are:

    Dynamic RLS using USERPRINCIPALNAME()  and a security mapping table.

    Report-level toggles (disconnected slicer + measures/filters) to switch between PU/HR views within the user’s authorized data.

    Separate roles/reports if different security contexts are mandatory.

    So the workarounds I shared earlier will help you simulate the toggle experience, but the true RLS logic can’t be driven by slicers.

v-sshirivolu's avatar
v-sshirivolu
Community Support
11 months ago

Hi raju8004212 ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

 

raju8004212's avatar
raju8004212
Frequent Visitor
11 months ago

Hi v-sshirivolu 

still the problem is not solved because we are not able to pass vailable to rls power bi wont allow to pass variables to rls ,its having a mechanism like rls then slicer not like reversal.

we are still looking for solution to solve the problem.
please connect with me on whatsapp +918341789398 too discuss more on this 

  • v-sshirivolu's avatar
    v-sshirivolu
    Community Support
    11 months ago

    Hi raju8004212 ,
    To clarify it isn’t possible to pass slicer values or variables into RLS. Power BI always applies     RLS first (based on user identity), and only afterwards slicers/filters.

    That means a “toggle RLS by slicer” design isn’t supported. The only supported approaches are:

    Dynamic RLS using USERPRINCIPALNAME()  and a security mapping table.

    Report-level toggles (disconnected slicer + measures/filters) to switch between PU/HR views within the user’s authorized data.

    Separate roles/reports if different security contexts are mandatory.

    So the workarounds I shared earlier will help you simulate the toggle experience, but the true RLS logic can’t be driven by slicers.

  • v-sshirivolu's avatar
    v-sshirivolu
    Community Support
    11 months ago

    Hi raju8004212 ,
    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