Summary: Date range filters in reports are applying UTC boundaries rather than the user's configured time zone, causing data to appear offset by several hours.
Symptoms
- Work orders completed late in the evening appear in the following day's report
- Morning appointments are excluded when filtering for the current date
- Report totals differ from expected values when filtering by date range
- Time zone setting in Account > Preferences > Regional Settings is correctly configured but not honored
Affected Versions
FieldPulse 3.2.0 – 3.2.4. All report types. Web application only; mobile reports are not affected.
Cause
The reporting engine's query builder converts date range inputs to UTC before filtering against the database timestamp fields. The conversion step is not applying the user-level time zone offset.
Workaround
Adjust your date range to compensate for the UTC offset:
- Calculate your time zone's offset from UTC (e.g., Eastern Daylight Time is UTC-4)
- Extend your date range by one day on each boundary
- Export to CSV and filter locally in your spreadsheet application
Alternatively, use the API to retrieve data with explicit UTC timestamps and apply time zone conversion in your external tool. See How do I retrieve custom field values from a work order via the API? for related patterns.
Status
Fix targeted for FieldPulse 3.3.0. The engineering team has implemented time zone-aware date parsing; currently in QA validation.