Semarchy xDM Component Release Notes

This page lists the main features added to the Semarchy xDM Component.

Change Log

Version 2023.1.8

Bug Fixes

  • DI-8917: Missing P_USERNAME declaration in Oracle database process flow.

Version 2023.1.3

New Features

  • DI-7382: xDM tools parameters order and labels aligned on Metadata definition.

Bug Fix

  • DI-7689: The synch parameter of the INTEGRATION xDM template is ignored.

  • DI-7330: The legacy Semarchy xDM metadata variable is missing from the internal resources, which leads to reference errors when using legacy flows.

Version 2023.1.2

Bug Fix

  • DI-7212: Semarchy xDM tools fail at execution time if their properties are automatically retrieved from the metadata.

Version 2023.1.1

Bug Fixes

  • DI-7119: In the Integration Semarchy xDM template, the values mapped to the LoadID column are ignored.

  • DI-7090: In the Cancel Load xDM tool, the DoCleanupSDTables action does not work on MSSQL databases.

  • DI-7100: In the Integration Semarchy xDM template, the subquery generated in the Insertion of rows in target actions is incorrect.

  • DI-7103: In the Integration Semarchy xDM template, the Load Status Variable Path option is not taken into account.

Version 2023.1.0

New Features

  • DI-5866: Microsoft Azure SQL Database is now supported in the xDM tools.

  • DI-6082: The xDM tools now use the fully qualified name of USR_XDI_PROCESS when operating on that table.

  • DI-6531: New xDM finger tab in the server node of supported database metadata allows defining xDM-specific parameters, used to manage the Load ID.

  • DI-6533: New Load Id Session Variable Path parameter added to the xDM tools. This parameter allows specifying the path and name of the variable storing the Load ID.

  • DI-6536: The INTEGRATION Semarchy xDM template is now available for incremental data integration into Semarchy xDM tables.

  • DI-7068: The ETL_PROCESS table has been renamed to USR_XDI_PROCESS.

Bug Fix

  • DI-5027: In the Semarchy xDM Integration template, the column delimiters on generation conditions are handled only for SQL Server, which leads to syntax errors on other databases using different delimiters.

  • DI-6121: The program name used by the Get Load ID tool has been changed from Stambia to Semarchy xDI.

Version 5.3.7 (Component Pack)

Bug Fixes

  • DI-6121: Change the program name used by the Get Load ID tool from Stambia to Semarchy xDI.

Version 5.3.6 (Component Pack)

New Features

  • DI-5866: Support Microsoft Azure SQL databases.

Version 3.0.0 (Component Pack)

New Features

  • DI-4962: Improved component dependencies and requirements management