📰 We have case-sensitive news You can now control of how your string filters match data with new case sensitivity settings at both the explore and field levels! What's new Configure case sensitivity for all your string filters (equals, contains, starts with, ends with, include, not include): • Set

case_sensitive: false

on an explore to make all string filters case-insensitive by default • Override at the field level for specific dimensions that need different behavior Example configuration

# Make all filters case-insensitive by default
models:
  - name: users
    meta:
      case_sensitive: false
    columns:
      - name: email
        meta:
          dimension:
            case_sensitive: true  # But keep email case-sensitive

Breaking change To make all filter operators consistent, INCLUDE and NOT_INCLUDE filters now respect case sensitivity settings and default to case-sensitive matching. Previously: INCLUDE/NOT_INCLUDE were always case-insensitive Now: They follow your

case_sensitive

setting (default: true) Let us know if you need assistance with this migration! Case sensitivity is available from version 0.2538.0 and the breaking change is planned to be released next week. -- Update March 3rd -- We heard your feedback 🙌 A lot of you told us that being able to control case sensitivity at the project level would make this breaking change much easier to manage. Good news! You can now do exactly that 🎉 Example

# lightdash.config.yml
defaults:
  case_sensitive: false  # Project-wide default

This is available in

v0.2557.0

(and don’t forget to update your CLI too!).