Forum Discussion
Filtering data on selected language
Hi Boeboey ,
Thanks for reaching out to the Fabric community. You’re good, and We appreciate you sharing details along with snapshots they make troubleshooting much easier. We wanted to build on your approach and address the challenges you mentioned regarding RLS and filtering.
1. Since RLS prevents users from pinning visuals to dashboards, you might want to reconsider using it for this scenario. Instead, a better approach would be to dynamically filter translations without RLS.
2. To do this, you can create a measure or calculated column that pulls the correct translation from the Safety Codes table based on the Selected Language measure. This method ensures flexibility and keeps your reports dynamic.
3. Your data relationships are structured correctly! Keeping Department and Function separate enables independent lookups for each, which works perfectly with your unpivoted Safety Codes table.
I hope this helps..
Hi Boeboey ,
Thanks for reaching out to the Fabric community. You’re good, and We appreciate you sharing details along with snapshots they make troubleshooting much easier. We wanted to build on your approach and address the challenges you mentioned regarding RLS and filtering.
1. Since RLS prevents users from pinning visuals to dashboards, you might want to reconsider using it for this scenario. Instead, a better approach would be to dynamically filter translations without RLS.
2. To do this, you can create a measure or calculated column that pulls the correct translation from the Safety Codes table based on the Selected Language measure. This method ensures flexibility and keeps your reports dynamic.
3. Your data relationships are structured correctly! Keeping Department and Function separate enables independent lookups for each, which works perfectly with your unpivoted Safety Codes table.
I hope this helps..
Thanks V-yubandi-msft for the advice!
I got rid of the RLS approach.
I have extended the original overview table:
with the columns language and.
Then I have duplicated the row for each language ("amount of languages" times row 1, ...).
And for each row, I took the translation in the language of that row.
E.g.
In this way, I had the language, all codes and the translations in this language for the codes for each event in 1 table. The language column of this table is now used as slicer across all pages.