Skip to main content
Inspiring
Jan 21, 2026 2:15 PM UTC
Question

Custom Record Field Extracting Partial Date Issue

I am using custom record field to extract completedOnDate (custom field) from completedOn(date and time) field. But there are sceanrio where ,when I am changing time zone ,date returned is still in gmt but not according to user timezone because of this when I am quering like below,few extra work items are displayed
a!queryFilter(
field: 'recordType!{ee5aa46d-0228-430f-a794-1134a11fbcc0}CMGT_Task.fields.{d7e1c9a9-03ae-4bfd-bbe6-2edc7e8d915f}completedOnDate',
operator: "=",
value: today()
),
 How to fix this issue ,so that date is based on user timezone only and not in gmt

    3 replies

    shubhama926776
    Brainy
    Jan 22, 2026 5:38 AM UTC

    Simply use todate(local(fv!record.completedOn, timezone())) in a real-time custom record field.

    शुभम्
    stefanhelzle0001
    Brainy
    Jan 22, 2026 6:56 AM UTC

    Do you know whether Appian passes the locale of the user context into such an evaluation?

    vinodn3917
    Inspiring
    Jan 30, 2026 4:29 PM UTC

    Appian stores all DateTime values in UTC. Custom record fields are evaluated in UTC during sync, not per user. As a result, extracting dates from DateTime fields at the record layer can cause timezone mismatches. The recommended approach is to perform DateTime range filtering using user-timezone functions like today() at query time rather than relying on derived date fields.

    [emoticon:7e405c0fb3114c2594c00fd89a9d9667] Remove completedOnDate from filtering
     [emoticon:7e405c0fb3114c2594c00fd89a9d9667] Filter using completedOn BETWEEN startOfDay AND endOfDay
     [emoticon:7e405c0fb3114c2594c00fd89a9d9667] Convert DateTime → local timezone only in UI
     [emoticon:7e405c0fb3114c2594c00fd89a9d9667] Avoid timezone logic in record sync