Gunnstein Lye added a comment - 18/Dec/15 12:53 PM The same will happen with DateAndTime, possibly also Date, if you set it to 1970-01-01 00:00. These store time as seconds. The solution should be to differ between `null` and zero here.

Stéphane Diot added a comment - 21/Dec/15 10:17 AM - edited Ok the problem here comes from the REST API, after testing the steps to reproduce the bug, here is the field that I have in the Version Update Struct for a time field set to "00:00": "field":[{ "id":731, "fieldDefinitionIdentifier": "new_eztime_1", "languageCode":"eng-GB", "fieldValue":0 }] We can see that the fieldValue is correctly set to 0 (the time is transformed to a number of milliseconds). Then when the Content item is fetched from the REST API, the same field is available in the Content returned by the REST API as: "field": [{ "id": 731, "fieldDefinitionIdentifier": "new_eztime_1", "languageCode": "eng-GB", "fieldValue": null }], The fieldValue is now null, so it seems 0 is transform to null somewhere server side.

Bertrand Dunogier added a comment - 02/Feb/16 2:39 PM FYI, related to EZP-25375 , but not fixed by the PR from [~yannick.roger@ez.no] .

Bertrand Dunogier added a comment - 02/Feb/16 4:12 PM After testing, The PR from EZP-25375 makes 00:00 usable as an input value, but still stores NULL in the database (needs to be fixed as well). If `ezcontentobject_attribute.data_int` is set to 0, the REST API returns the expected value: { "id": 491, "fieldDefinitionIdentifier": "time", "languageCode": "eng-GB", "fieldValue": 0 } But PlatformUI will still show "Empty value", meaning that there is a bug in PlatformUI itself.

Yannick Roger (Inactive) added a comment - 09/Feb/16 9:55 AM This issue will be taking care of in EZP-25375