REST converting ISO dates in character fields to US dates

[klincecum (Kevin Lincecum)]

@ridgea

I had a scenario were a UBAQ in a dashboard kept subtracting a date by a day were the time element was midnight.

I think we covered that in these two threads:

REST date/datetime bug reality check

If someone has a few minutes can I beg a favor? We’ve got a new bug we’re working on with support and in the interest of helping them help me I’m curious if it’s just us or not. When you pass a date through a BAQ, a date value 2023-01-01 returns as “1/1/2023”. I’d attach a BAQ as a means to replicate but it would take longer to import than to write from scratch: select (cast('20230101' as date)) as [Calculated_foo] Until recently, when I retrieved that via REST I’d get 2023-01-01T00:00:00-0…

Date Values in BAQ Results via REST API

As of version 2023.1.6, I am seeing a change in the way dates are returned via the REST API, compared to past versions. It has broken our software integrations that rely on BAQs. For example, I have a BAQ that I am running in versions 2022.2.12 and 2023.1.6. The BAQ returns at least one date field. The actual date value from the database is ‘2023-05-17’. Value Returned from BAQ via REST API 2022.2.12: “2023-05-17T00:00:00-05:00” 2023.1.6: “2023-05-16T19:00:00-05:00” The above example is a …