When a root record is updated by a business entity services call, field values from a child record with a low trust score can be the surviving record value.

When a parent record that has multiple child record levels is unmerged, the records at the grandchild level are assigned an incorrect foreign key.

In a WebSphere environment, the ReadBE business entity service generates the following error:

SIP-50101: You do not have the required privileges to view the business entity SupplierProductServices. To request additional role privileges, contact your MDM administrator.

In an IBM DB2 environment, the GetLookupValues SIF API generates the following error:

SIP-14129: The unique ID is not valid. The UID format must be "<table name>|<column name>".
SIP-10323: There is no column with the name <Lookup column name>.

The Search Record REST API returns deleted child records.

A call to the Tokenize API fails with the following error:

SIP-16011: Failed to gather metadata

Even though a POST request to the WriteBE business entity service updates a single child record or a parent record field, the lastUpdateDate value for the parent record and all the child records of a business entity are updated.

When external calls are configured, validation messages do not appear in the localized languages.

Multithreaded SearchMatch API requests fail with errors.

When you use the registerCustomTableObject SIF API to register custom jobs on staging tables, you cannot add or remove the jobs in the batch group.

The

defaultPageSize

and

recordsToReturn

parameters do not work for the Search Record REST API.

When you use the Delete SIF API to delete a child record, the deleted child record incorrectly matches in a match job.

By default, a Put or Cleanse Put call applies BVT calculations to all fields in a record instead of the fields specified in the SIF request.

Verbose error message could potentially leak information.

A second level dependent lookup ignores the parent dependency and returns all values.

After JVMs are restarted, servers are incorrectly marked as fully started even though some modules did not complete initialization.

Occasionally, when you run SIF commands on cross-reference records, the following error occurs:

SIP-40609: Cannot edit the record. 
The PERIOD_REFERENCE_TIME that you specified is not within the effective period for the record you are editing.

After the executeBatchUnmerge SIF API runs, the relationship between C_B_PARTY and C_B_PARTY_ALT_ID is not set correctly.

When an exact match rule includes columns from child records, the Find Duplicates operation returns child records that do not match.

The Delete Business Entity REST API cannot delete child records in a business entity. The REST API fails with a null pointer exception.

If you use the depth parameter when you implement pagination, a REST API request does not return any results.

REST calls fail when the global identifier (GBID) contains the hyphen (-) character.

The search REST API performance is poor when you retrieve multiple business entity records with depth > 2. To fix this issue, the

cmx.server.enrichcopager.thread_pool

and

cmx.server.enrichcopager.min_rec_for_multithreading

properties are introduced.