Replication data is now removed when a matching table's configuration is deleted.

Performance was improved when changing the state of a batch of records.

An enhancement was made to improve performance when validating a dataset where the add-on is active.

FasterXML Jackson library was updated to version 2.15.2.

Swagger JAXRS2 library was updated to version 2.2.15

The false positive icons on records are not removed in the Manage group screen after deleting the records from the metadata service.

The Search before create service cannot be executed when the Matching fields tab includes invalid matching fields.

In workflows, the Search before create screen cannot be re-accessed after performing an inline merge and updating a record in list of potential duplicates.

An exception is thrown when no duplicates are found in a group.

A foreign key field should only be able to use the Exact matching algorithm.

The error message from the previous phase is not cleared after changing the field.

Merged records should not be changed to Unset when modifying non matching fields and a merge policy isn't defined for the default matching policy.

Records that include the '+' character in the primary key cannot be viewed when accessing their group.

An issue occurs when switching algorithms in the data comparison node.

Color properties are not applied correctly.

The tooltip for Enable matching is not localized in the Administration pane.

A different method should be used to detect whether a table belongs to a Business object, or individual table configuration.

The incorrect survivor field value is used when multiple records satisfy merge function conditions.

A field configured for use in matching operations cannot be configured for other relationships. For example, in a Person table the Address field is configured through matching by foreign key. This field cannot be configured in another instance with a different relationship (over linked table, or none).

Linked records are duplicated in the link table when one of the foreign keys is not part of the primary key.

When matching using the foreign key option, you can only specify a single hop foreign key. In other words, it cannot be a foreign key to a foreign key.

The Validation service in the Consolidated view runs as expected when first executed, but slow on subsequent executions.

In order to accurately track record lineage, table history must remain activated over time. If the table's activation status repeatedly changes, the lineage data will be inconsistent.

Severe errors occur when multiple datasets based on the same model exist and a table from one of these datasets is activated in an add-on matching configuration. As a workaround, you can create another data model publication using the Manage publications service in the Data Model Assistant. After creating a dataset for the new publication, you can follow the normal procedures to configure a matching policy for tables in the new dataset.

For foreign key alignment, the FKs that are multi-value fields cannot be aligned (either manually or automatically).