Using ESRI 10.5.1 Enterprise geodatabase SQL Server 2016
I have a layer with a field'START_STAMP' defined as datetime2(7)
Using an ESRI Edit Service I insert a row specifying an attribute as
"START_STAMP": 1543479941234
I then use the same EDIT Service to retrieve the row and the attribute shows as
"START_STAMP": 1543479941000
IE the timestamp has been truncated to the nearest second.
This is not the behavior I wanted (or expected)
Is there any way that I can avoid the truncation, or do I have to live in a world where a second is as close as I can get to the time?
