December 2025: Infrastructure & Platform Enhancements

The December 2025 release deploys a series of improvements to Data Lake Sync. These changes improve stability of the platform, increase error handling and provide additional features to customers. 

Maintenance Window Definitions

This release includes a major feature release, Maintenance Windows. A Maintenance Window can now be defined by each customer; Customer-Defined Maintenance Window. Between the start and end time of the customer-defined maintenance window, no schedules will be executed for that tenant. This allows customers to schedule their own platform maintenance and ensure Data Lake Sync will not execute during that time. 

In addition to Customer-Defined Maintenance Windows, Data Lake Sync now has the concept of a Global Maintenance Window. This is a product-wide maintenance window. Between the start and end dates, all Data Lake Sync schedules for all customers will not execute. This will be primarily used for ensuring Data Lake Sync does not execute during the Infor monthly maintenance. 

The existing Data Lake Sync portal will be updated to include these two features. 

Enum Columns

Infor Data Lake allows for columns of type Enum. This column type has no defined width in the Infor Data Lake. Prior to this change, Data Lake Sync read the allowed values for each Enum column and set the width of the destination column to be that width. This relied on customers ensuring the Infor Data Lake had the latest metadata from the ERP. This change sets a minimum width of 30 characters for each Enum column, reducing the risk of stale metadata causing a Data Lake Sync failure. 

NOTE: This first execution of Data Lake Sync after this release will issue multiple ALTER statements to the database to extend any Enum columns that are less than 30 characters to a length of 30 characters. Depending on data volume and database performance, this could cause a longer-than-expected sync execution. 

Logging improvements

Enhanced logging for schedules can now be applied. A flag on the schedule now controls if increased log levels are enabled. This log level includes additional information on schedule progress.

Error Handling improvements

Once data has been loaded from Infor Data Lake into the customer destination database TMP tables, a stored procedure is executed to merge this data in to the base table. Additional error handling has been added to that stored procedure execution for all relevant database types to ensure any issues found during the merge step are logged, and errors are thrown.  

 Notification improvements

The existing success/failure notification process remains unchanged. A change has been made to the email subject line. Previously the subject line was 

❌ Data Synchronization Failed

❌ Data Synchronization Failed: <schedule name>