报告编辑者可以更改过滤条件子句的条件或值，但无法更改 Looker Studio 中的过滤条件字段。如需更改导入的 LookML 过滤条件，请在 Looker 中修改底层 LookML 模型。
数字过滤条件类型仅支持使用用户输入的非 null 值的匹配（高级）条件。
匹配（高级）条件在 Looker Studio 和 Looker 中的行为略有不同。在 Looker 探索中，Looker 可能会根据用户的输入，将匹配（高级）条件转换为更合适的条件。如果用户的输入不适用于 Looker Studio 支持的其他过滤条件，Looker Studio 会将匹配（高级）选项用作万能条件；不过，Looker Studio 不会转换该条件。如需详细了解可与匹配（高级）条件搭配使用的过滤条件值，请参阅 Looker 过滤表达式文档页面。
Looker Studio 不支持所有 Looker 过滤条件。如果 LookML 模型定义的 conditionally_filter 参数或 always_filter 参数使用了 Looker Studio 不支持的过滤条件，Looker Studio 会显示过滤条件为“为 null”。报告编辑者必须手动更新过滤条件和值。下表显示了 Looker Studio 支持的 Looker 过滤条件，其中 Looker 过滤条件的编写方式与 Looker 探索中显示的形式相同，并且包含等效的 Looker Studio 过滤条件：
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-25。"],[],[],null,["# Understand Looker Explore data on a Looker Studio report\n\nAfter Looker has been [established as a data source](/looker/docs/studio/connect-to-looker) for your report, you can add fields, charts, and filters that are based on data from a Looker Explore to your report.\n\nBecause they are defined by [LookML](/looker/docs/what-is-lookml) parameters, the fields and filters for a Looker data source may appear or behave differently than the fields and filters for other data sources in Looker Studio or from how they appear in Looker. This page describes these nuances and how to interact with fields and filters from a Looker data source.\n\nLearn more about how to [add data to a report](/looker/docs/studio/add-data-to-a-report) and how to [edit fields in your reports](/looker/docs/studio/edit-fields-in-your-reports).\n\nHow Looker Explores appear in Looker Studio reports\n---------------------------------------------------\n\nIn a Looker Studio report that uses Looker as a data source, an Explore and its [views](/looker/docs/reference/param-view-view), [dimensions](/looker/docs/reference/param-field-dimension), [dimension groups](/looker/docs/reference/param-field-dimension-group), [measures](/looker/docs/reference/param-field-measure) (known as *metrics* in Looker Studio), and [joins](/looker/docs/reference/param-explore-join) are displayed in a different format from how they appear in Looker. Both the Looker Explore field picker and the Looker Studio report field picker organize fields alphanumerically by type (dimensions, followed by measures or metrics) under the name or [label](/looker/docs/reference/param-explore-view-label) of the Explore. However, the Looker Explore field picker further groups fields by the [view](/looker/docs/reference/param-view-view) or [view label](/looker/docs/reference/param-field-view-label) by which the fields are defined.\n\nFor example, in Looker, an Explore called **Flights** has the views **Carriers** , **Destination** , **Flights** , and **Origin** . The **Carriers** view has the dimensions **Carrier Name** , **Code** , and **Name**. No LookML view labels have been specified. The fields as appear like this:\n\nIn the corresponding Looker data source called **Flights - FAA** , Looker Studio displays these dimensions as **Carriers Carrier Name,** **Carriers Code** , and **Carriers Name** . The dimensions from other views appear in the same list of dimensions. For example, **Destination City** is a dimension in the **Destination** view.\n\nHow Looker Explores behave in Looker Studio reports\n---------------------------------------------------\n\nA Looker data source in Looker Studio is based on a Looker Explore, which is defined in a Looker [model's LookML](/looker/docs/lookml-terms-and-concepts#model). Looker developers use LookML to describe dimensions, aggregates, calculations, and data relationships in an organization's SQL database. Some LookML parameters are applied in the Looker data source but not surfaced in Looker Studio. The following sections describe the LookML parameters that are applied in the Looker data source and that you can interact with in Looker Studio.\n\n### Drill fields and links\n\nDrill fields and links that are defined with the [`drill_fields`](/looker/docs/reference/param-field-drill-fields) and [`link`](/looker/docs/reference/param-field-link) LookML parameters are available to Looker Studio report viewers in the **[Drill Actions](/looker/docs/studio/drill-into-your-data)** menu on Looker Studio table charts.\n\nSee the [Drill into your data](/looker/docs/studio/drill-into-your-data) documentation page to learn more about using drill actions in Looker Studio.\n\n#### Things to know about drill actions in Looker Studio\n\nKeep the following information in mind when you're using drill actions (drill fields and links) with a Looker data source:\n\n- They are supported only on [table charts](/looker/docs/studio/table-reference).\n- They are supported only for Looker dimensions and dimension groups.\n- If they are imported from Looker, they are read-only. To make changes to imported drill actions, [edit the underlying LookML model](/looker/docs/lookml-validation) in Looker.\n\n### Filters\n\nReport editors can define [persistent filters](/looker/docs/studio/about-filter-properties) (at the chart, group, page, and report level), [quick filters](/looker/docs/studio/add-a-quick-filter), and [controls](/looker/docs/studio/about-controls) in Looker Studio reports based on fields from the Looker data source.\n\nLooker Studio indicates which fields have been defined in the Looker data source's underlying LookML as filters or filter-only fields. Looker Studio also displays suggestions for filter values based on the data source's LookML [`suggest_dimension`](/looker/docs/reference/param-field-suggest-dimension) and [`suggest_explore`](/looker/docs/reference/param-field-suggest-explore) definitions when **Equal to (=)** and **In** conditions are used. To see filter value suggestions, enable **Show suggested values while typing** in the filter editor. Any predefined default values will be pre-selected.\n\nViewers can access and modify any of the report's editable filters by clicking the report's **More options** menu and selecting [**View applied filters**](/looker/docs/studio/about-filter-properties).\n\nIn reports that use a Looker data source, filters that have been defined with LookML parameters are referenced in Looker Studio as described in the following table:\n\nIf [`sql_always_where`](/looker/docs/reference/param-explore-sql-always-where), [`sql_always_having`](/looker/docs/reference/param-explore-sql-always-having), or [`access_filter`](/looker/docs/reference/param-explore-access-filter) parameters are included in the underlying LookML model, they will be applied to the data source but won't be visible in Looker Studio.\n\n#### More about filters that are always or conditionally required\n\nKeep the following information in mind when using conditional LookML filters:\n\n- You can't remove filters that are either conditionally or always required from a chart.\n- Report editors can make changes to a filter clause's [condition or value](/looker/docs/studio/configure-filter-conditions) but can't change the filter field in Looker Studio. To make changes to imported LookML filters, [edit the underlying LookML model](/looker/docs/lookml-validation) in Looker.\n- The numeric filter type supports the **Matches (advanced)** condition with the user-entered **not null** value only.\n- The **Matches (advanced)** condition behaves somewhat differently in Looker Studio and in Looker. In a Looker Explore, Looker may convert the **matches (advanced)** condition to a more appropriate condition, based on the user's input. Looker Studio uses the **Matches (advanced)** option as a catch-all condition when the user's input is inappropriate for the other filter conditions that Looker Studio supports; however, Looker Studio doesn't convert the condition. For more information about the filter values that you can use with the **Matches (advanced)** condition, see the [Looker filter expressions](/looker/docs/filter-expressions) documentation page.\n- Looker Studio doesn't support all [Looker filter conditions](/looker/docs/filtering-and-limiting#basic_filters). If a LookML model defines a `conditionally_filter` parameter or an `always_filter` parameter that uses an a filter condition that is not supported by Looker Studio, Looker Studio displays a filter condition of **Is Null** . Report editors must manually update the filter conditions and values. The Looker filter conditions that Looker Studio supports are shown in the following table, with the Looker filter condition written as it would appear in a Looker Explore and the equivalent [Looker Studio filter condition](/looker/docs/studio/configure-filter-conditions):\n\n#### More about filter-only fields\n\n| **Warning:** The LookML parameter that is called \"[`parameter`](/looker/docs/reference/param-field-parameter)\" differs from Looker Studio [parameters](/looker/docs/studio/parameters). The LookML`parameter` creates a filter-only field that can be used to filter Explores, Looks, and dashboards but that can't be added to a result set. Looker Studio parameters collect and pass user-supplied values to calculated fields and connectors.\n\n- To make changes to imported filter-only fields, such as [specifying the values](/looker/docs/reference/param-field-parameter#specifying_allowed_values) that a user can input, [edit the underlying LookML model](/looker/docs/lookml-validation) in Looker.\n- When a report editor edits a filter that uses a filter-only field, they must use an AND operator and can't include the same filter-only field. The available values are defined in the Looker data source's underlying LookML.\n- Advanced filter controls are unavailable for filter-only fields that have [allowed values](/looker/docs/reference/param-field-parameter#specifying_allowed_values) defined in the underlying LookML.\n- Looker Studio doesn't support all types and values for filter-only fields. If a LookML model defines `parameter` or `filter` parameters that use an unsupported type, Looker Studio displays a filter condition of **Is Null**. Report editors must manually update the filter conditions and values. The supported filter-only field types are shown in the following table:\n\nRelated resources\n-----------------\n\n- [Looker and Looker Studio shared terms and concepts](/looker/docs/looker-and-studio-shared-terms-glossary)\n- [Add data to a report](/looker/docs/studio/add-data-to-a-report)\n- [Edit fields in your reports](/looker/docs/studio/edit-fields-in-your-reports)"]]
