Data Exporter - Reclassify Custom Fields of Type "DateTime" to "LocalDateTime"

Currently, date-time type custom fields are classified as DateTime in the Data Exporter Manifest when they should be classified as a LocalDateTime. DateTime fields have a Zulu offset intended for Coordinated Universal Time (UTC), but the date-time of custom fields is supposed to be for locally observed date/times.

With the April 2021 release, Cornerstone is reclassifying custom fields of type "DateTime" to "LocalDateTime" within the Data Exporter. This reclassification will fix the incongruity by presenting the date-time without the Zulu offset.

This functionality is available in Stage portals as of April 13.

Organizations must review and update their integrations to make sure that during parsing of the export, the validation step will not fail when it encounters the new date-time type.

Manifest Before Change Manifest After Change

Custom_Field_0001

"type": "datetime"

Custom_Field_0001

"type": "Localdatetime"

 

Output for Custom field_001 before change Output for Custom field_001 After change
"2008-09-22T14:01:54.9571247Z" "2008-09-22T14:01:54.9571247"

Implementation

This functionality is automatically enabled for all organizations using the Data Exporter.

This functionality is available in Stage portals as of April 13.