< class="prominent-subhead ">

SQL Server SmartObjects drop milliseconds from DateTime values

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.


When saving DateTime values to a database, the millisecond values are dropped.


For example: the value passed is 6:47:08.128, but the value returned is 6:47:08.000.


A fix for this issue is planned in an upcoming update (as of 5/9/2018) however, there is a workaround available.

To resolve this, edit the database's corresponding SmartObject and change the associated data type for your DateTime table column to Text.