Case sensitive slicer when using direct query

[wardy912]

Hi everyone,

 We have a Power BI report connected to Fabric using Direct Query, the slicers are case sensitive.

There doesn't seem to be any option to change this.

Does anyone have any ideas?

Thanks

[v-tsaipranay]

Hi @wardy912 ,

I wanted to follow up on our previous suggestions regarding the issue. We would like to hear back from you to ensure we can assist you further.

Thank you.

[v-tsaipranay]

Hi @wardy912 ,

Thank you for reaching out to the Microsoft fabric community forum. Also thank you @vivien57 and @danextian  for your helpful response.

To clarify, slicer visuals in Power BI do not have a built-in option to ignore case sensitivity. Since you are using DirectQuery to a Lakehouse, Power Query transformations and calculated columns in the model are not available. This means you need to handle case sensitivity either by adding a column at the data source level (such as using UPPER() or LOWER() in your Lakehouse), or by switching to Direct Lake mode, which would let you create calculated columns in Power BI.

So in practice, you have two options:

• Stay with DirectQuery: Handle case formatting directly in the Lakehouse (SQL view or Notebook transformation).
• Switch to Direct Lake : Add a calculated column in the model to standardize the text values.

Either of these will ensure your slicer behaves consistently without splitting values based on case.

Hope this helps. Please reach out for further assistance.

Thank you.

[danextian]

Create a column in the source that removes can sensitivity - either lower or uppercase the entire text string.

[wardy912]

Thanks @danextian 

 I'll give that a go

[Rupak_bi]

Hi @wardy912 ,

You can well create a calculate column in power query. check that out... 

[wardy912]

Thanks @Rupak_bi 

 unfortunately, it's direct query so that's not an option

[vivien57]

Hello @wardy912 ,

No, there is no option in the ‘Slicer’ visual.

I don't know what your Fabric data source is, but you need to consider managing the case sensitivity issue (lower/upper) in the data source.

If you weren't using a direct query, you could have created a calculated column.

Are you sure you're using a direct query and not a direct lake ?

Please feel free to give a kudo and validate the solution if it suits you.

Have a nice day,

Vivien

[wardy912]

Thanks Vivien,

 It's direct query connecting to a lakehouse (which as I write this, makes me think we should use direct lake).

Would changing to direct lake fix the issue?

I'll look into a fix for the column in the notebooks

[vivien57]

Hi @wardy912 

This would allow you to create a calculated column in the model (powerBI) to manage case sensitivity (without managing it at the data source level).

Please feel free to give a kudo and validate the solution if it suits you.

Have a nice day,

Vivien