How to Re-apply a Control Filter to a Single Table in Looker Studio

Looker Q&A Looker Studio
1

Current Situation
The report contains several tables and charts, each connected to a different data source (multiple Google Sheets or different tabs within the same sheet).
All of these visualizations are controlled by a single filter control called “Self-ID” (“自家番”).
Only one table—“Medical Treatment History” (“診療治療歴”)—is no longer affected by this control filter. All other tables and charts are filtered correctly.
Goal
I want the “Medical Treatment History” table to once again respond to the existing “Self-ID” control filter.
What I’ve Tried
I selected the control filter and looked at the properties panel, but I couldn’t find any interface to specify which components it should filter.
I selected the “Medical Treatment History” table and tried to add a filter from the properties panel, but couldn’t find an appropriate option.
I checked the properties of other tables that are working with the control filter; they don’t appear to have any special filter settings—yet they are successfully filtered by “Self-ID.”
Question
How can I specify which components a control filter applies to (i.e., set the elements that it filters) in Looker Studio?
Thank you for your help.

1 Like
2

Hi,

Since you mentioned Self-ID, which appears to be a unique identifier across all your Google Sheets data sources, it is best to treat it as a primary key. As part of your data preparation, I recommend combining all your datasets into a single master sheet using Google Apps Script. This approach ensures that the Self-ID field is consistent across all records and avoids problems where filters fail because different sheets have mismatched field names, data types, or structures.

By creating one master dataset, all charts and tables in Looker Studio will point to the same data source. This will make the Self-ID control filter work reliably across every visualization without needing separate troubleshooting for each table. It also improves performance, simplifies maintenance, and reduces errors caused by mismatched joins or missing fields in blended data.

In the long run, this method makes your reports easier to manage and more stable. Instead of debugging filter issues caused by multiple sources, you will only maintain one clean, well-structured dataset. This ensures that any future filters, calculations, or dashboard changes will work smoothly and consistently across the entire report.

1 Like
3

Grouping components is the way to apply specific filters to a particular table or chart, then there are page wide filters which applies to the entire page irrespective of groups. using these 2 you must be able to control the filter logic.

there might be 2 possibillities here :

  1. The Grouping has not been done
  2. “Medical Treatment History” table does not have self-ID as a dimension
1 Like
4

Hey,

Hope you’re keeping well.

In Looker Studio, a filter control only affects charts or tables if the field it’s based on exists in that component’s underlying data source and matches exactly in name and type. If your “Medical Treatment History” table stopped responding, first open the table’s Data tab in the properties panel and confirm that the “Self-ID” field is present in that data source and spelled exactly the same as in other sources. If the field differs (e.g., different column name in Google Sheets), you’ll need to rename or create a calculated field so it matches. Once the field aligns, the control filter will automatically apply without needing to manually link it to specific components.

Thanks and regards,
Taz

1 Like
5

Hi, thank you very much for your detailed and helpful suggestion.

I fully understand the benefits of treating the Self-ID (our Jikaban) as a primary key and consolidating all data into a single master sheet for stability and simplified filtering.

However, in our current setup, the datasets across the different sheets contain a different number of records (rows), reflecting distinct transaction types and data granularity (e.g., daily milk volume vs. specific treatment history). Because of this variance in the record count and data structure across the sheets, it is not feasible for us to simply combine them into a single, unified master sheet using Google Apps Script at this time.

We are currently required to maintain the data in its original, separate sheet structure.

Given this constraint, we are specifically looking for a way to restore the cross-data-source filtering functionality within Looker Studio, as it was working previously.

Thank you again for the excellent suggestion on best practices!

6

Hi Taz,

Thank you very much for your advice and for the reminder about the strict requirement for field name and type matching in Looker Studio’s cross-source filtering.

I fully understand that the filter functionality depends on the exact match of the “Self-ID” field across all underlying data sources.

I have already followed this specific guidance by ensuring the field name (“Jikaban” / “Self-ID”) and the data type (Numeric/Text) are unified and consistent across the control’s data source and the target table’s data source. However, the “Medical Treatment History” table is still not responding to the filter, even though other components are working correctly.

I will continue troubleshooting the data source connection and field definitions based on the excellent advice I’ve received.

Thank you again for your time and expertise.

Best regards,

7

Hi,

Thank you for clarifying the filter logic regarding Grouping components and page-wide filters. That explanation is very helpful for understanding the control scope.

Regarding your two possibilities:

  1. Grouping: I have tried grouping the control and the “Medical Treatment History” table, but it did not resolve the issue.

  2. Missing Self-ID: I can confirm that the “Medical Treatment History” table does have the “Self-ID” (our Jikaban) as a dimension, and I have confirmed the field name and data type are identical to the control’s source.

The core problem remains that the table is not accepting the filter, even though its data source contains the matching key. I will continue to troubleshoot the connection and try a few more methods to restore the functionality.

Thank you again for your continued support!

Best regards,