> For the complete documentation index, see [llms.txt](https://docs.antsomi.com/cdp-365-user-guide-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antsomi.com/cdp-365-user-guide-en/insights/reports/make-reports-interactive/use-controls-across-data-sources.md). # Use controls across data sources Understand how filter controls work in reports with multiple data sources. In a report based on a single data source, a control affects all the charts and other controls in the report. In reports with multiple data sources, how the control works depends on the data sources involved. As a general rule, controls can filter charts from different data sources as long as the data sources share the same internal structure (schema). In practice, this means that you can filter across data sources if: a) the data sources were created using the same [connector](broken://pages/-Mfu_7rDnMq08jKjFL44), and b) the data sources have a fixed schema, with a predefined set of fields. For example, a control based on the Google Analytics *Country* dimension applies to all components on the page that also use a Google Analytics data source, even if they connect to different views. This is because all Analytics data sources have the same default field set. (Note that optional features in Analytics, such as Enhanced Ecommerce, will produce additional fields that may not exist in all Analytics data sources, and therefore, not be compatible with controls based on properties or views without those features.) Filtering across data sources generally won't work if the charts involved are based on data sources of different types, even if the fields have the same visible name. This is because filtering is based on the *internal* field IDs, not the visible field names in the data source. (And, once a field has been created in the data source, you can't edit the internal ID.) ### Example Say you have a report with 3 different data sources: one from Google Sheets, and two from Analytics. Even if all three data sources include a field with the visible name of "Country," only the Analytics data sources share the same internal structure. A control for the Analytics charts can use the *Country* dimension from either data source, but it won't filter the Google Sheets chart. Conversely, a control based on the Sheets *Country* dimension will filter the Sheets-based chart, but won't affect the Analytics charts. The embedded report below illustrates the limits of cross data source filtering. * Controls don't affect charts based on data sources with different schemas * This report includes 3 data sources: one from Google Sheets (left) and 2 from Analytics (right). * The Analytics-based control affects both of the Analytics-based charts because their data sources share the same schema. * The Sheets-based control only affects the Sheets-based chart, because its schema doesn't match the Analytics data source schema. * (The internal names of the dimensions are different between Sheets and Analytics.) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.antsomi.com/cdp-365-user-guide-en/insights/reports/make-reports-interactive/use-controls-across-data-sources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.