IssueTracker

Description:

We are encountering an issue when using Looker connections within Looker Studio. Specifically, the problem arises with "Filter Only" fields that are set up in Looker and then used within Looker Studio.

Issue Details:

Behavior:

When "Filter Only" fields from Looker are used in the Looker Studio Setup tab under the Filter panel, the field type is not being considered. Example: For instance, if a "Filter Only" field is of type Date in Looker, when we attempt to use this field as a filter in Looker Studio, the only comparison operator available is "Equal to (=)". This limitation prevents us from utilizing these fields effectively, as it restricts the filter options to only exact matches.

Expected Behavior:

When a "Filter Only" field is of type Date, we expect to see appropriate filtering options (such as "Before", "After", "Between", etc.) that are typical for date fields. This would allow for a more flexible and accurate filtering of data. Impact: This issue severely limits the usability of date fields as filters in Looker Studio and affects our ability to create dynamic and meaningful reports.

Steps to Reproduce:

Connect Looker as a data source in Looker Studio. Create a report and add a "Filter Only" field from Looker that is of type Date. Go to the Setup tab and add a filter using this "Filter Only" field. Observe that the only available filter option is "Equal to (=)", regardless of the field type.

Please investigate this issue and provide guidance or a fix to ensure that "Filter Only" fields respect their field types when used as filters in Looker Studio.