-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: 2021.0
-
Fix Version/s: None
-
Component/s: Rest API
-
Tags:
-
Backlog priority:850
-
Story Points:3
Steps to reproduce :
- define a field "stop_timestamp" of type Integer
- create a document and set the property "stop_timestamp" to 1668176372345619999
- observe that the view panel display this property with the value 1668176372345620000
- click on the Edit button and observe that the field "stop_timestamp" also contains 1668176372345620000 instead of 1668176372345619999
- running a REST call to fetch the document returns the same value
"properties": { "sch_recording:stop_timestamp": 1668176372345620000 },
Expected result: the REST call (and the UI) displays the entered value = 1668176372345619999
- links to