When the filter type is “Custom filter” (equals, contains, starts with, etc), it would be great if we could get an option to specify if we want it to be case-sensitive or not. Most of the time, we don’t want it to be case-sensitive but that’s currently the only option.
The workaround of creating a calculated field (at the analysis, dataset or data source level) that’s all in lower case doesn’t always work.