This task applies to a source with selectable, complete date fields, such as an appropriately typed spreadsheet source. Some connectors choose a fixed date-range dimension. Google's current documentation uses the Data Studio name at the linked destination; the report setting discussed here is Date range dimension.
Reconcile the selected record IDs
This original fictional fixture has one row per shipped order, no returns, one shipment per order and amounts in dollars:
| Order | order_date | ship_date | Amount |
|---|---|---|---|
| O1 | 2026-02-27 | 2026-03-02 | 100 |
| O2 | 2026-03-10 | 2026-03-12 | 60 |
| O3 | 2026-03-30 | 2026-04-02 | 80 |
For an inclusive March 1–31, 2026 range, order_date selects O2 and O3, totaling 140. ship_date selects O1 and O2, totaling 160. Both calculations use the same source amounts. A report question about March shipments requires the second record set.
Google's date-range documentation, checked October 24, 2026, explains that the Date range dimension determines which records a date filter selects. It also notes that Google Ads and Google Analytics sources set that dimension automatically and do not allow changing it.
Ask for the field choice before a new formula
Help diagnose a Looker Studio revenue scorecard; do not edit a report.
Question: dollars on orders shipped during March 2026.
One row is one order, one shipment, amount in dollars; no returns.
Fixture:
O1 order_date=2026-02-27 ship_date=2026-03-02 amount=100
O2 order_date=2026-03-10 ship_date=2026-03-12 amount=60
O3 order_date=2026-03-30 ship_date=2026-04-02 amount=80
Metric: SUM(amount). Date filter: March1 through March31 inclusive.
Data source/connector and date-field types: [PASTE].
Chart Date range dimension/default date range/control scope: [PASTE].
List selected IDs and total under order_date and ship_date separately.
Explain which field answers the stated question. Identify chart-level
overrides and connector restrictions to inspect before changing it.
Keep date selection separate from a comparison-period percentage.
Do not invent a native report result or change source dates/amounts.
OpenAI's prompting guidance supports giving the context that changes the answer. Include the actual chart properties, not just a screenshot of the date control.
Inspect the native chart properties
In an editable copy, select the scorecard and inspect its Setup properties. For a source that permits the choice, select ship_date as the Date range dimension. The field must represent a complete date including year, month and day. A month-name string does not provide that boundary.
Check the chart's default date range and the scope of the date control. A custom range on the component can differ from the report setting. Temporarily add a detail table using the same source, date configuration and filters so you can reconcile the included IDs. Under the stated fixture settings, the target is O1 and O2 totaling 160.
Comparison dates answer a second question, such as change from the previous period. Disable that comparison while reconciling the base total, then restore it with an explicit period definition. A percentage comparison cannot explain which date column selected the underlying March records.
The Tableau running-total guide covers calculation traversal after marks are selected. For this report, retain the business date definition, chosen dimension and included IDs with the checked total. If a real order can have several shipments, define the shipment-level amount allocation before extending this one-shipment fixture.