Hello Thinkwise,
We are experiencing an issue where a SQL DATE column (subsidiary_calendar.date) is serialized by Indicium as a UTC datetime string ("2025-06-08T00:00:00Z") in the OData response. The Thinkwise Universal GUI running in the Netherlands (CEST = UTC+2) subtracts 2 hours, rendering the date as the previous day.
This causes a visible bug in our pickup overview: Monday June 8 disappears from the day window because Sunday's is_work_day = 0 ends up being shown on Monday's slot.
We confirmed this via a direct OData call:
GET /subsidiary_calendar?$filter=subsidiary_id eq 1186 and date eq 2025-06-08&$select=date,is_work_day
Response: { "date": "2025-06-08T00:00:00Z", "is_work_day": 0 }
The database correctly stores 2025-06-08 with is_work_day = 0 (Sunday). The serialization introduces the offset.
We know that $apply=Compute(Date(date) as date) returns a pure date string as a workaround, but this cannot be applied at SF model level since our views and subjects are driven by the model.
Is there a way to configure Indicium or the SF model so that DATE columns are returned as a pure date string ("2025-06-08") without a UTC timezone offset — for example via a domain setting, column property, or Indicium configuration flag?
Kind regards,
Rolf
working_days as (
select sc.subsidiary_id, sc.[date],
row_number() over (partition by sc.subsidiary_id order by sc.[date]) as rn
from subsidiary_calendar sc
where sc.is_work_day = 1
and sc.[date] between cast(getdate() as date) and dateadd(day, 14, cast(getdate() as date))
),
workingdays_in_future as (
select subsidiary_id, [date] as max_date from working_days where rn = 7
)
