Custom Object Date fields display correctly in the object list (e.g., 2025-11-13), but appear one day earlier in Dashboard widgets when using Daily breakdown. This only happens with Custom Object Date fields — not with CreatedAt or UpdatedAt.

How to Reproduce:

Create a Custom Object with a Date field (date-only picker).

Add records with any date (example: 2025-11-13).

Build a Dashboard widget:

Metric: any number field

View By: Date

Breakdown: Daily

Date Property: the Custom Object’s Date field

View the chart in a non-UTC timezone (ex: US/Central).

The dashboard plots the record under 2025-11-12, one day earlier.

Audit Log Proof:

Audit log shows the Date field is stored exactly as:

{ "properties": { "date": "2025-11-13" } }

There is no time component, so the Dashboard renderer should not be applying a timezone shift.

Expected Behavior:

A Custom Object Date field stored as YYYY-MM-DD should appear on that same date in Dashboard charts, especially when using the Daily view.

Actual Behavior:

Dashboard internally treats the date as midnight UTC, applies timezone offset, and shifts it to the previous day (e.g., US/Central: −6 hours).

It does not seem to occur with CreatedAt/UpdatedAt dates.

Impact:

All dashboards relying on Custom Object Date fields show incorrect day buckets for anyone outside UTC.