SmartObject incorrectly saving datetime as 2001-01-01 00:00:00.000
kbt151857
PRODUCTK2 Five
K2 blackpearl
K2 smartforms
BASED ONK2 blackpearl 4.7
TAGSMicrosoft SQL
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.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
Issue
In this scenario:
- We created a SmartObject with a datetime property.
- Then added an entry which includes a valid datetime.
A workflow will alter some properties of that SmartObject entry and save, but does not have an input for the datetime, so it should not be changed. However, it is incorrectly overwriting the datetime property as 2001-01-01 00:00:00.000.
