May 2026

Stay updated with Syniti's latest releases and enhancements in enterprise data management. Check out our release notes for May 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.

May 18, 2026

Syniti is excited to announce that the Syniti Knowledge Platform and Migrate public APIs now support OAuth 2.0 authentication. This enhancement provides a more secure and standardized method for accessing our public APIs, enabling seamless integration with third-party applications and improved user data protection.

Key Benefits

• OAuth 2.0 is now available as an authentication method for all Knowledge Platform and Migrate public API endpoints.

• Developers can implement industry-standard authorization flows, including client credentials and authorization code grants.

• Enhanced security for user data and API access.

To get started using OAuth 2.0 with our public APIs, refer to the OAuth 2.0 Authentication section.

May 14, 2026

Syniti is back with another release, enhancing Migrate with expanded PostgreSQL capabilities, including metadata schema querying in the SQL Editor. The Mappings interface now displays the Usage Level field as a default column. This release also includes comprehensive bug fixes for PostgreSQL stability, ETL rule generation, Value Mapping imports, and permission controls.

Keep reading for more detailed information on this release.

Enhancements

Migrate

• SQL Editor now supports querying PostgreSQL metadata schemas (pg_catalog), enabling users to access system catalogs for troubleshooting, performance analysis, and diagnostic queries.

• On the Mappings > Source Mappings page, the Usage Level field is now added as a standard default column, instead of requiring users to manually add it via More Grid Options > Choose Columns.

Bug Fixes

Migrate

• We fixed an issue where certain System Reports failed to load with an "Unable to execute the provided query" error, and where refreshing MIG_ tables in Snapshot Management could fail due to mismatched column mappings.

• We fixed an issue where the Refine Rule (Mapping Assist) button in Migrate returned errors or irrelevant AI-generated suggestions with large datasource schemas. Migrate now sends only the relevant tables and columns to the AI service, and properly handles oversized requests with clear error messages.

• We fixed an issue where auto-generated ETL Rule names for PostgreSQL databases could exceed the 63-character limit, causing build failures on subsequent builds.

• We fixed an issue where a failed Value Mapping configuration reimport would delete existing value mapping records, resulting in data loss.

• We fixed an issue where the View Snapshot Management role did not properly restrict users from adding, deleting, or dropping tables.

• We fixed an issue where inactive Column Translations > Phrase Out values were displayed in reports.

• We fixed an issue where PostgreSQL working databases could encounter a "Connection pool has been exhausted" error during normal usage. The Clear Connection Pool option is now available for PostgreSQL datasources, consistent with the existing support for SAP HANA working databases.

• We fixed an issue where the MIGRATE schema and its required objects (such as xtvaluemap and list_target_value tables) were not automatically created in PostgreSQL working databases, causing errors when selecting source mappings with check tables.

• We fixed an issue where running a Postload report with NUMERIC columns on PostgreSQL working databases failed with a runtime error in the syn_postload_compare function.

• We fixed an issue where clicking the Rule Name field in the Edit ETL Task dialog box cleared the existing rule name value, potentially unlinking the ETL rule if the task was saved in that state.

• We fixed an issue in the SQL Editor where DDL definitions for backup tables stored in the SYNDDL table were truncated, resulting in incomplete view definitions.

• We fixed an issue where the "In Progress" build status value was not accepted during the Excel template upload process in Mappings, causing an import error due to inconsistency with the previous "In-Progress" format.

• We fixed an issue in the SQL Editor where PostgreSQL connections did not set the schema in the search_path, requiring users to enter two part name in SQL queries.

May 5, 2026

Syniti is back with another release. This release focuses on stability and performance improvements for Replicate Preview, addressing critical issues related to replication execution performance and record count display accuracy. Additionally, a patch release for Syniti Replicate Desktop v11.0.1.14 is now available, bringing important updates to the desktop application.

Keep reading for more detailed information on this release.

Bug Fixes

Replicate Preview

• We fixed a performance issue that caused slowness in replication execution due to auto-scaling not functioning as expected.

• We fixed an issue where the Replication Details page incorrectly displayed the in-progress record count as failed records during active replications.

Replicate Desktop

A patch release for Syniti Replicate v11.0.1.14 is now available. Refer to Syniti Replicate v11.0.1.14 - Patch Release for more information.