The January 2026 release deploys a series of improvements to Data Lake Sync. These changes improve stability of the platform and increased error handling.
Implementation of Hard Delete feature
Data Lake Sync previously passed down the 'Deleted' flag from the Infor Data Lake to the destination database. This maintained a perfect synchronization between Infor Data Lake and the destination database. The Hard Delete feature allows customers to specify at a table level if Data Lake Sync should delete the record in the destination table. This feature removes the need for customers to add WHERE Deleted='False' downstream. This feature is optional and defaulted to off. In most cases, customers use data downstream, and delete detection should be implemented in the downstream solution. Hard Delete is supported in SQL Server, Oracle and Postgres destinations.
Improved error handling for merge failures
In a previous release, we added additional error handling to stored procedure execution for all relevant database types to ensure any issues found during the merge step are logged, and errors are thrown. This release includes enhancements to that error handling to provide reasons for failure.
Improved connection drop handling
Additional redundancy to connection drop has been added through improved timeout detection and improved handling of connection errors.
Improved metadata handling for variation number column
Data Lake Sync previously required the variation number column to be stored in Data Lake Sync. This release removes the need for that and adds a dynamic look up to Infor metadata to detect the variation number column.
Other Minor Changes
- Data Lake Sync version number added to log file
- Improvements to backend log rotation
- Other minor backend changes for reliability and general improvements
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article