Bug Report: Drop-down lists fail with System Error when using "Manage field names and IDs" (Cross-filtering)

[hokuto_mnm]

I am experimenting with the new “Manage field names and IDs” feature to enable cross-filtering between different data sources without using Data Blending. I have encountered a specific bug where the feature works for some controls but fails for others.

The Issue: I have overridden the Field IDs for two different data sources (Google Search Console and Google Sheets) to share a common ID (e.g., common_id). When I use this field in a control, the behavior is inconsistent:

• Input Box (Advanced Filter): Works perfectly. Entering a value filters charts from both data sources correctly.

• Drop-down List (and Fixed-size List): Fails immediately. It displays a “Configuration is invalid” (System Error) message, and the list values are not populated.

Steps to Reproduce:

1. Open a report with two data sources: Google Search Console (URL Impression) and Google Sheets.

2. Go to Resource > Manage field names and IDs.

3. Override the ID for the “Query” field in GSC and the “Keyword” field in Sheets to a matching new ID (e.g., shared_key_01).

4. Add a Drop-down list control to the report and set the Control Field to the overridden field.

5. The error “Configuration is invalid” appears.

Environment & Notes:

• Data Sources: Google Search Console, Google Sheets.

• Verification: I have tested this using both a custom ID string and the system reserved ID (_QUERY_). Both result in the same error for Drop-downs, while both work for Input Boxes.

• Hypothesis: Since the Input Box works, the ID mapping itself is succes

  sful. The issue seems to be specific to how the Drop-down control queries/aggregates the list of values when an ID override is active on a native field.

Request: Please investigate this behavior. This feature is a great alternative to Data Blending, but it is currently unusable for reports that require Drop-down selection menus.

[a_aleinikov]

Hi @hokuto_mnm This looks like a current limitation or bug in how Drop down controls handle overridden Field IDs

Input Box works because it sends a direct filter value without needing to query and aggregate distinct values from the data source Drop down controls first request a list of unique values for that field and when the Field ID is manually overridden across different native connectors like GSC and Sheets the control likely cannot resolve a single valid schema so it throws Configuration is invalid

Since the same ID works for text input but fails for value listing the mapping itself is accepted however the Drop down control probably requires a stable backend field definition and does not fully support cross source ID overrides yet

At the moment this feature appears partially supported for cross filtering but not for controls that need to generate selectable value lists The safest workaround is still Data Blending or using a single unified data source until Google fixes this behavior