Date field regression in v13: typed date shortcut parsed to wrong month (possibly ZK 10 related)

48 views
Skip to first unread message

Bambang Irawan

unread,
Jul 20, 2026, 10:00:29 PM (8 days ago) Jul 20
to iDempiere
Hi all,

After upgrading from v12 to v13, typed date shortcuts are parsed incorrectly.

In v12, typing "1/1/26" in a date field (e.g. Account Date in Statement of Accounts, login language English, format dd-MMM-yyyy) was parsed as 01-Jan-2026. In v13, the same input becomes 01-Jul-2026 — the month is ignored and defaults to the current month, so users now have to pick the date from the calendar.

I suspect this is related to the ZK 10 upgrade (client-side parser can't match the numeric month against the MMM token and falls back to today's month).

Is this a known issue or already fixed in a recent daily build? Happy to open a Jira ticket if not.

Thanks,
Bambang Irawan1.png
2.png

Carlos Antonio Ruiz Gomez

unread,
Jul 21, 2026, 6:08:20 AM (7 days ago) Jul 21
to idem...@googlegroups.com
Yes, most probably a fix in zk.

I think is not a bug.

Your format is dd-MM-yyyy so zk interprets  1/1/2026 as just a 1.  If
you enter 1-1-26 (the separator matches the format) then it works as you
expect.

Regards,

Carlos Ruiz
> Bambang Irawan --

Reply all
Reply to author
Forward
0 new messages