DEV+RELEASE Date fields input broken

Report a Bug
1

DEV: 2025-04-10
RELEASE: 2.2.0

Regional setting : Date format is set to ISO8601 date format (YYYY-MM-DD)

Date fields problem

The date field shows and accepts ONLY mm/dd/yyyy, despite the regional setting being ISO8601 and the help text in field definition telling me “To paste in a date use the following format: YYYY-MM-DD”

  • there is NO way to enforce input/output of ISO8601 date format

AND: trying to enter e.g. 07 01 2024 (without typing the spaces!) - while starting to enter the year number month and day - a reset to “dd” and “mm” occurs - i.e. field content killed
i.e. NO manual input is possible - ONLY via the slower date picker

AND copy from one field to another at the SAME dialog does NOT work

AND copy from external via clipboard in format YYYY-MM-DD (as described in default help text) does NOT work

2

Note: Comparing RELEASE and DEV I found that

  • in RELEASE it is possible to enter a date manually if one DOUBLE CLICKS in a field instead of single click - in format YYYY-MM-DD - after successful saving it is still displayed (correctly but wrong format) as mm/dd/yyyy

  • in current DEV I can enter the date as in the release version but in contrast I can NOT save -
    The JS console shows:

main.ec058b092d52f38d.js:1 ERROR TypeError: Cannot read properties of undefined (reading ‘public_id’)
at U.editObject (main.ec058b092d52f38d.js:1:203992)
at main.ec058b092d52f38d.js:1:207662
at nb (main.ec058b092d52f38d.js:1:3196614)
at Object.y [as next] (main.ec058b092d52f38d.js:1:3196787)
at J.next (main.ec058b092d52f38d.js:1:2122382)
at ge._next (main.ec058b092d52f38d.js:1:2122050)
at ge.next (main.ec058b092d52f38d.js:1:2121736)
at main.ec058b092d52f38d.js:1:2119672
at a (main.ec058b092d52f38d.js:1:2146825)
at b3.next (main.ec058b092d52f38d.js:1:2119511)

3

Thanks for the detailed report. The bug has been confirmed and a ticket has been created in our Jira: DAT-1544.

The save functionality should work on the development version as well — could you please share a screenshot so we can take a closer look?

Best Regards,
Abdullah

4

Hi,

Weirdly the problem did NOT occur on another system with dev 2025-04-08.

That I could not save with the dev version was possibly be caused by my
“version on the fly switching trick”. See my previous mail.

I rechecked with the “trick” and version DEV 2025-04-09 and recognized that by
refreshing with F5 (after the "switching trick) saving now WORKS.

So I think the part with the not saving became obsolete - it works in DEV.
Therefore I did not create a screenshot.

The other points for the date fields still apply, though!

Sorry for causing you probably confusion because of my workaround “trick”
caused problem.

cu
Holger