Openui5: DateRangeSelection UTC: true doesn't work

[ekansh005]

OpenUI5 version: initially found on 1.60.6 but valid for the latest version 1.68 as well

Browser/version (+device/version): Chrome

Any other tested browsers/devices(OK/FAIL): same behaviour

URL (minimal example if possible): https://next.plnkr.co/edit/9AdLQkPKASV0uQhQ

Steps to reproduce the problem:

1. Select today's date and some other date of future for DateRangeSelection
2. Select today's date in Date Picker

What is the expected result?
Since 'UTC: true' is set in format option of both the controls, today's date should have been formatted in the same way for DateRangeSelection and DatePicker.

What happens instead?
DatePicker considers the UTC: true flag but DateRangeSelection doesn't. Due to this, DatePicker shows the correct UTC formatted Time and is received correctly (same date) on ABAP backend where both are binded with DATS type but dates coming from DateRangeSelection are yesterday's dates.

Any other information? (attach screenshot if possible)
type:'sap.ui.model.type.Date' is set on DatePicker but when used with DateRangeSelection, the values are null in the binding.

[hristop]

Hi @ekansh005,

This is how the control was designed to work. It is designed to take into account only the dates and set the first hour of the first day and the last hour of the second data.

Best Regards,
Hristo

[ekansh005]

Hi @hristop,
I just checked the fiori design guidelines and API reference of this control and didn't find a mention of this way of working (first and last hour). Even if this is how it is ought to be working, still it could support the UTC format when developer sets it to true. In terms of UTC support, it should behave exactly how DatePicker works (specially since it extends the DatePicker).
My requirement use case is completely satisfied by this control except the fundamental error of UTC support which results in wrong date in backend.

[hristop]

Hello @ekansh005 ,

I have created an internal incident 1970418432.
This way the colleagues can have a look into this and provide further information.
The status of the issue will be updated here in GitHub.

Regards,
Hristo

[gerym]

Hi @ekansh005 ,

We have updated the documentation with described above behavior of DateRangeSelection.

Kind Regards,
Gery

[ekansh005]

Thanks @gerym for updating the documentation.
But don't you think that developers should have this functionality as an option in this control? a possible enhancement?

BR, Ekansh