Skip to main content

Power BI

New

Parameter selection by key value pairs (semantic name - value)

Vote (11) Share
Carlos Kynäslahti's profile image

Carlos Kynäslahti on 01 Feb 2017 16:55:31

If you create a list or a query of parameter values, there is no way to set a different display value to the actual value used. So if I need to filter a report with a non-semantic code, I'm unable to give the end user a semantic display value. For example, let's assume the code for "Detergent" is "8199387", I'd have to display the user the value "8199387" instead of the semantic string "Detergent".

Comments (5)
Carlos Kynäslahti's profile image Profile Picture

a3309361 99be-ea11-a812-000d3a8ddfb2 on 06 Jul 2020 00:07:31

RE: Parameter selection by key value pairs (semantic name - value)

This would be ridiculously helpful, make this a priority please!

Carlos Kynäslahti's profile image Profile Picture

a3309361 99be-ea11-a812-000d3a8ddfb2 on 06 Jul 2020 00:07:31

RE: Parameter selection by key value pairs (semantic name - value)

We really need this, as a business we need our reports translatable, the saving of a slicer value only captures the "Text" within the slicer so if you switch language the corresponding translated text cannot be matched, with a value this would work seamlessly

Carlos Kynäslahti's profile image Profile Picture

a2c35231 2331-4b1e-a46d-75559a66382a on 06 Jul 2020 00:07:31

RE: Parameter selection by key value pairs (semantic name - value)

This is needed for translated systems

Carlos Kynäslahti's profile image Profile Picture

e09101eb 778c-42e2-84fc-34b1eb4f8dc6 on 06 Jul 2020 00:05:08

RE: Parameter selection by key value pairs (semantic name - value)

I strongly support this idea, creating my first report in power bi , very disappointed that we don't have any such feature in power bi , even when we have this feature in SSRS.

Carlos Kynäslahti's profile image Profile Picture

964c8c73 cbab-4fae-bc44-956197edb6f9 on 05 Jul 2020 22:55:59

RE: Parameter selection by key value pairs (semantic name - value)

Has anyone been able to find a workaround to this until this feature is released ?