Enhance date fields in feature services to support millisecond resolution when adding, editing, or querying features.
We have feature service which writes date to MS SQL database, even thouth we have datetime2(7) data type fields, feature service writes only seconds. For example - when you try use aply edits operation and put 1543479941234 value to the datetime field, it will be cut to seconds, when you try to force service to write miliseconds (trying "DateTimeField" : "2020-10-06 11:11:11.34" ) it will bee decline by the server.
It is imposible to use ESRI Feature Service to work with highly accurate time data.
Now, date fields in Enterprise Geodatabases can't handle millisecond values if the table/feature class is stored in MSSQL-based Enterprise Geodatabase. In field of geophysics this feature would be essential.
See this related idea: https://community.esri.com/ideas/16842-add-time-to-arcgis-pros-units-page
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.