The can_filter parameter lets you prohibit a dimension or measure from being used as a filter. For example:
dimension: description {
can_filter: no
}
-
The default value of can_filter is true, meaning that dimensions and measures can be used as filters as you would expect. However, there may be some cases when a field may be too demanding to search (like a large text description), and in these situations you can prevent that field from being used as a filter. Users will simply not see a FILTER option when they hover over the field.
Note that can_filter cannot be used with:
Measures of type: list, because they cannot be filtered on anyway
filter fields, which only exist for the purpose of filtering
Additionally, drilling into a field will not be permitted if the drill requires a filterable dimension and the can_filter parameter is set to no. This occurs when you:
Attempt to drill on a dimension that uses can_filter: no
Attempt to drill on a measure if a can_filter: no dimension is used in the same query as that measure
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[],null,["# can_filter\n\n\u003cbr /\u003e\n\nUsage\n-----\n\n```\nview: view_name {\n dimension: field_name {\n can_filter: yes \n }\n}\n```\n\nDefinition\n----------\n\nThe `can_filter` parameter lets you prohibit a dimension or measure from being used as a filter. For example: \n\n dimension: description {\n can_filter: no\n }\n\n-\n\nThe default value of `can_filter` is true, meaning that dimensions and measures can be used as filters as you would expect. However, there may be some cases when a field may be too demanding to search (like a large text description), and in these situations you can prevent that field from being used as a filter. Users will simply not see a **FILTER** option when they hover over the field.\n\nNote that `can_filter` cannot be used with:\n\n- Measures of [`type: list`](/looker/docs/2512/reference/param-measure-types#list), because they cannot be filtered on anyway\n- [`filter`](/looker/docs/2512/templated-filters) fields, which only exist for the purpose of filtering\n- The [`filters`](/looker/docs/2512/reference/param-field-filters) parameter that is used with measures\n\nAdditionally, drilling into a field will not be permitted if the drill requires a filterable dimension and the `can_filter` parameter is set to `no`. This occurs when you:\n\n- Attempt to drill on a dimension that uses `can_filter: no`\n- Attempt to drill on a measure if a `can_filter: no` dimension is used in the same query as that measure\n\nSee the documentation pages for [`drill_fields` (for fields)](/looker/docs/2512/reference/param-field-drill-fields) and [`drill_fields` (for views)](/looker/docs/2512/reference/param-view-drill-fields)."]]