Bug Mx5.20 ListView: Non-localized Date is stored as a Localized Date

EDIT: I did some more research and I think I have pinpointed the bug. We have recently migrated from Mendix 5.8.1 to Mendix 5.20. In 5.8.1 there was no problem. In 5.20, when I use the datepicker widget to set the value of a non-localized DateTime attribute in a listview, the value is stored as a localized value instead (causing all kinds of timing problems in our application). ORIGINAL POST: This is what I do in Mendix 5.20: Create an entity 'TestEntity' with one DateTime attribute 'Date' with Localize = No. Create a form, add a TestEntity datagrid and generate the New/Edit button forms. In the same form, add an editable TestEntity listview. Use the datagrid New button to create a TestEntity object and use the datepicker widget in the pop-up to set Date to 22-12-2015. The resulting Date value is: UTC time: 2015-12-22 00:00:00.000 Session time: 2015-12-22 01:00:00.000 +0100 The TestEntity object I just created, appears in the listview. Use the datepicker widget in the listview to once again set Date to 22-12-2015. The resulting Date value is UTC time: 2015-12-21 23:00:00.000 Session time: 2015-12-22 00:00:00.000 +0100 Why is the resulting Date value different? Any ideas? Thanks!
1 answers

It turned out to be a Mendix bug. Mendix has accepted and solved the ticket through a hotfix. I assume the fix will be released for Mx versions 5.21.2+