Stay updated with Syniti's latest releases and enhancements in enterprise data management. Check out our release notes for January 2026 to discover new features and improvements designed to drive your data migration, quality, and governance strategies, as well as your digital transformation efforts.
For information on planned features and enhancements of future releases, refer to Upcoming Releases.
January 7, 2026
Syniti is excited to announce the release of Rule Mapping Assist, a new feature that provides AI-powered assistance for Rule and RuleXref mapping actions in Migrate > Mappings. This release also includes multiple enhancements, bug fixes, and performance improvements across Migrate to ensure a more stable and efficient user experience.
Keep reading for more detailed information on this release.
New Features
Migrate
Rule Mapping Assist
Syniti is excited to release Rule Mapping Assist, an AI-powered rule mapping assistant, designed to accelerate and standardize the migration mapping rule workflow in Syniti Migrate. This feature enhances both efficiency and consistency by enabling users to convert initial mapping rule descriptions into precise, structured mapping definitions and by supporting the automated generation of SQL/DDL statements and ETL tasks in alignment with the SynitiONE Methodology.
Currently, Rule Mapping Assist supports Rule and RuleXref mapping actions when the ETL tool is Syniti Migrate ETL.
Key Features
Refined Mapping Rule Descriptions: Converts initial rule descriptions and metadata into precise mapping definitions and proposes required source fields.
Automated SQL/DDL Generation: Generates proposed SQL or DDL directly from refined mapping definitions, reducing manual development effort.
In-App Preview and Validation: Allows users to run generated SQL in-app to validate results before saving. Simple rules persist to a field; complex rules produce SQL views and ETL jobs.
Iterative Editing: Supports re-running refinement or SQL/DDL generation, with only saved outputs retained to improve results.
Refer to Rule Mapping Assist for more information.
Enhancements
Migrate
Field names in MIG_ views of the SRCCONSTRUCT snapshot datasource are now standardized to use uppercase.
The ETL tab’s version and ETL Version Selection list now display the Environment next to the Milestone identifier in the following format: <Milestone> - <Environment>.
When copying ETL Jobs, you can now select the required ETL types to copy to the next Environment in the ETL Version Selection dialog box.
You can now run the DDL script in Edit ETL Task > Rule DDL for ETL tasks that use a view or stored procedure, allowing you to view and validate the results.
Bug Fixes
Migrate
We fixed an issue where generated SQL code for reading the Value Mapping’s Check table did not filter by the intended Target Datasource when multiple Target Datasources were present. This fix now adds a DATASOURCE filter to the generated SQL code.
We fixed an issue where the Environments column on the Datasources page displayed incorrect values for datasources that do not use environments when their purpose is set to System.
We fixed an issue where segmented reports accessed from the Deployment Reports page generated exported files with incorrect report data.
We fixed an issue where dragging and dropping to sort ETL Tasks did not update their index, affecting the ETL Task execution sequence.
We fixed an issue where boolean data type columns in reports from PostgreSQL databases did not allow True or False values when filtering records.
We fixed an issue where the CLOB and SDO_GEOMETRY data types from Oracle did not have equivalent mappings in PostgreSQL.
We fixed an issue where executing a script in the SQL Editor for PostgreSQL databases did not function as intended.
We fixed an issue where the Priority field was not displayed in the Migration Reports and Deployment Reports grids.
We fixed an issue where the SQL Editor failed to run a script when opened from the Rule DDL tab of an ETL Job.
We fixed an issue where refreshing a report triggered a foreign key conflict error with the ZDEPLOY field in the working database.
We fixed an issue where editing Report Links in Target Reports caused the system to highlight and select the wrong report, especially when multiple reports were linked or had similar names.
We fixed an issue where users were unable to select and copy the SQL statement from Report DDL and ETL Rule DDL.
An error message is now displayed when pre-validation rules for an ETL job fail.
We fixed an issue where the SQL Editor failed to execute ETL scripts for PostgreSQL databases when queries were spread across multiple lines.
We fixed an issue where the Publish toggle for Target Reports would not retain its state after being turned on or off.
We fixed an issue in Mappings where setting the Build Status to Reject in the Data Mapping Details pane did not update the Build Status column in the Mappings pane after saving.
We fixed an issue that caused certain numerical values to export incorrectly in CSV exports when the Alternate Leading Zero Format option was enabled.
We fixed an issue where the Insert rule in Dataset Transform ETL failed to include fields from datasets if the field name did not begin with a ‘Z’ prefix.
We fixed an issue where attempting to import system datasource tables in Snapshot Management resulted in the following error: Unable to translate column datatype FLOAT(126,0) from Oracle to SQL Server.
We fixed an issue where downloading reports from the Migration Reports page resulted in an “Invalid column name” error when column names contained special characters.
We fixed an issue where the percentage graph in the PMO Dashboard did not display the configured color correctly.
We fixed an issue where users with read-only access were able to copy ETL Jobs into a different environment.
We fixed an issue where the log messages were not available on the Debug Logs page when a Release Copy operation errored out or completed.
We fixed an issue where changes to the Mapping Report Index in Target Reports were not reflected in the corresponding Deployment Reports.
When running an ETL Job, clicking the Continue or Continue with Breakpoint button now displays a loading (spinner) icon until the job is complete.
We fixed an issue where table names created in Mappings using a PostgreSQL working database were generated in uppercase instead of the required lowercase format.
We fixed an issue where numeric fields in the PostgreSQL target table were assigned incorrect precision during Oracle table snapshot replication, defaulting to a precision of 22 instead of using the source precision.
We fixed an issue where the SKP Applications menu did not honor user security settings, causing users with access limited to Deployment reports in Migrate to see all SKP applications in the menu.
We fixed an issue where Repopulate jobs displayed an Error status while their step jobs remained stuck in the New status and did not progress further.
We fixed an issue where Refresh attempts failed due to report names in the PostgreSQL working database exceeding the 63-character view name length limit, resulting in errors during the refresh process.
We fixed an issue where disabling notifications for a source table in the Mapping > Sources panel incorrectly added a subscription for mapping notifications.
We fixed an issue where using the Copy To feature within ETL Job Environments caused some Job Queue steps to fail for ETL tasks marked as Inactive or for steps linked to an ETL_ID that did not exist.
We fixed an issue where clicking the Cancel button for a job in Migrate > Monitor > Job Queue failed to stop the job and did not change its status to Canceled.
We fixed an issue on the ETL Jobs page where manually added ETL tasks were hidden after the Build ETL process was executed.
We fixed an issue where creating a Boolean field from a PostgreSQL working database as a Binding Link caused the report to display no values for that field.
We fixed an issue where using Import Mapping and Datasets in Migrate > Administrator > Import caused all indexes on the new project to default to 10 in the Sources pane of Migrate > Mapping, instead of retaining the original project’s index values.
We fixed an issue on the Target Reports details page where clicking the Add (+) icon in the Report Links section did not expand the Select a Report to Link to grid to show the full report names.
We fixed an issue where CSV report downloads based on the calculated total number of cells (as determined on the Parameters page) did not work when viewing a report.
January 6, 2026
Syniti is back with another release featuring an enhancement to the system datastore connection forms. This release also includes required backend functionality in Construct to support the WebApp configuration auto-conversion process, along with essential bug fixes for Syniti Replicate Desktop.
Keep reading for more detailed information on this release.
New Features
Construct
Note
The auto-conversion to Construct Preview feature will be rolled out in phases on a tenant-by-tenant basis. It will be available to all tenants soon.
To prepare for converting your WebApps and construct pages from legacy Construct to Construct Preview, Syniti is deploying the necessary backend functionality to support the auto-conversion process.
Once converted, Administrators can review a summary of the conversion results, including migrated components, incompatible components, and components that require manual configuration for the next conversion iteration.
Existing legacy Construct WebApps will remain available for use. However, additional security configuration will be required in the SKP after conversion. Refer to the Post Conversion Checklist section for more information.
Refer to Review Converted WebApps for complete information on the conversion process.
Next Steps
Syniti will identify tenants that are ready for the conversion, and the auto-conversion feature will be enabled for selected tenants in a phased manner.
In preparation for the auto-conversion process, we highly recommend scanning all in-use datastores into the SKP Catalog. This action will help to optimize the conversion process. Refer to Scan a System Datastore for instructions on how to scan a datastore.
Enhancements
Catalog
You can now create connections using the dynamic properties form. Currently, the dynamic properties form is available only for a limited set of databases, and will be available for more databases in the future.
Existing connection and its properties will be migrated and parsed automatically to the dynamic properties form correctly, even if a connection was created using a connection string.
Databases With Dynamic Properties Form
Databricks
IBM Db2 OS/390
IBM Db2 LUW
Microsoft SQL Server
Oracle
PostgreSQL
SAP HANA
SAP systems via SAP NetWeaver
Snowflake
Note
The Metadata Scanning usage is not yet supported in IBM Db2 OS/390 and IBM Db2 LUW databases.
SNC support for SAP NetWeaver is currently under development. Although enabling SNC marks the password field as optional, users must still provide password credentials, as SNC is not yet supported.
Bug Fixes
Replicate Desktop
A patch release for Syniti Replicate v11.0.1.6 is now available. Refer to Syniti Replicate v11.0.1.6 - Patch Release for more information.
Note
Access our previous month’s release notes using the left navigation panel.