Case sensitive slicer when using direct query

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.