Support dynamic functions in Power BI filters (Report, Page, Visual). In particular USERCULTURE()

Use Case : Building Multi-language Reports in Power BI

In order to implement Power BI translations with Power BI Premium as documented here:

https://github.com/PowerBiDevCamp/TranslationsBuilder/blob/main/Docs/Building%20Multi-language%20Reports%20in%20Power%20BI.md

We need to use RLS or bookmarks to filter "field parameters" for the appropriate culture for data translations. It's not optimal and can lead to a mix of languages in the same report.

If we could create an hidden report filter that uses a DAX function, it would prevent that from happening (ex. Language[LanguageId] = USERCULTURE() )

Note: The USERCULTURE() DAX function returns the culture that the user selected in Power BI Service (or the default browser language).

Thanks for considering it (or voting for it)

Frederick