Time zone anomaly when using date only

🧩 Low-Code Development
#1

Hello,

I noticed a problem concerning datetime fields when they are “date only” format. CORTEZA 2023.3.4

Here an example :

  • Module 1 : “dateMin”, “dateMax”
  • Module 2 (sub module) : several records (with the field “date”)
  • Page View : block:record-list with a prefilter : date <= ‘${record.values.dateMax}’ AND date >= ‘${record.values.dateMin}’
  • Time zone of the server : UTC +2h

When we use a prefilter (query language) on datetime field on default settings, everything works like expected.

DATE-time
DATE-time1306×619 31.9 KB

On the other hand, when the date time fields are “date only”, the prefilter switches dates to UTC +0 :

dateOnly
dateOnly1253×689 32.7 KB

I think this might a be an bug/issue.

test.zip (2.6 KB)

Cheers,

#2

Thanks for reporting it, time zones are always fun!

1 Like
#3

Should be fixed as part of this issue (Updating a record when you have no read permission but have update for a required field raises required error · Issue #1853 · cortezaproject/corteza · GitHub)

1 Like