We found an unwanted behaviour in the filter option in our overviews (A12 2023.06-ext3).
When we set a DateTime-Filter the UI shows the time we picked, but the query parameter that gets set by the OverviewEngine automatically converts the time to UTC.
This basically renders the whole DateTime-Filter unusable for our customer.
You can see an example in the picture above.
Is there a way to prevent this behaviour? Is it maybe a configuration in the overview I missed?
Thank you in advance and with best regards,
Karin
Hi @karin-sparse-tundra, are you using timezone CET (UTC+01.00) in your application? It is configured in your document model.
When you select the date 28/03/2024 and time 11:30 with timezone +1, the date value will be “2024-03-28T10:30:00.000Z” in ISO format.
Please double-check the value below:
new Date("2024-03-28T10:30:00.000Z").toLocaleString("de-DE", {timeZone: "CET"})
The result will be “28.3.2024, 11:30:00”.
So your date value is
new Date("2024-03-28T10:30:00.000Z")
We only display this date in timezone CET (UTC+01.00) with your format, nothing is converted.
Dear @minh-firm-chasm , thank you very much for your input.
Yes, I just have changes the timeZone in the document model form UTC to CET.
If I understand you correctly. then the timeZone-setting in the model is just purely responsible for what is shown in the Frontend (the UI value), but the underlying data that will be sent to the Backend is still UTC.
I guess the fault was with us then and some dateformat conversions in the Backend that we should not have done. Thanks a lot!
