This update improves how the Import + Export module handles timezone settings for date and datetime fields.
Datetime fields, such as Application Date or Event timestamps, now apply the "use client configured timezone" option by default, ensuring timezone-accurate data on both import and export. Date-only fields, such as Date of Birth, Test/Evaluation Dates, and Custom Date Fields, no longer display the "use client configured timezone" option, since these fields do not include a time component and timezone conversion could shift the date by a day.
These changes apply to newly added or edited columns; existing transformations on existing imports and exports are not altered.
Datetime fields now apply timezone by default: When adding a datetime field to an import or export, the "use client configured timezone" option is enabled by default. This is the most significant change and ensures datetime values are accurately converted across timezones.
Timezone option removed from date-only fields: Date of Birth, Test/Evaluation Dates, and Custom Date Fields no longer display the "use client configured timezone" option, preventing unintended date shifts caused by unnecessary timezone conversion.
Existing transformations are preserved: This update does not alter existing transformations on existing imports and exports. However, adding a new column or editing an existing column for a date-only field will reflect the new behavior.
💡 Recommended Action: We encourage you to verify the behavior of these fields in current jobs. Ensure that you are using a Date Format transformation with the "use client configured timezone" option enabled for all datetime fields. Ensure that you are not using the "use client configured timezone" option when transforming date-only fields.
This update reduces the risk of inaccurate data during import and export by applying timezone-aware defaults to datetime fields and removing misleading timezone options from date-only fields.
