You cannot sort child columns in the search results panel of the

Search

tab.

When you create a query, you cannot select the correct child business entity fields without knowing the parent to which the child business entity belongs.

You cannot create or edit a record in the

Form

view.

After you get a validation error for a lookup field, you cannot save a correct value.

Search results do not display values for lookup fields with CHAR data type.

When you launch Data Director in Chrome 78 or later, field labels do not appear in the Cross-reference Records view.

When Data Director uses an HTTPS load-balanced URL, an error might occur when you perform actions such as opening and creating records.

When you open a record that has more than 1000 cross-reference records associated with it, the

ORA-01795

exception occurs.

When you display Data Director in a language other than English, the Status column in the task inbox is empty.

When you use the Hub Console to acquire a lock on the MDM Hub Master Database, the session ID is cleared for all the users who are logged into Data Director. Data Director generates the

SIP-18017

error.

When a business entity field with a label format contains pure numbers, the label appears as a date.

Pending records appear in the search query results.

The

Task Manager

has usability issues because of multiple scroll bars.

When you create a merge task for records with consolidation indicator 9, the merge process fails.

In the

Matching Records

view, the option to select all records is not available.

After a user claims a task or updates the task owner, the

Task Manager

does not automatically refresh to show the changes.

In the

Task Manager

, when you filter matching records by match rules, the following error appears:

SIP-50225: The Interaction ID of a pending merge record does not match the Interaction ID which was specified in the request.

When you search for lookup records, the records results do not populate in the Data Director Form view.

When you save the changes to a record that is in the pending state, an unclear error message appears.

Records that users remove from the merge task participate in the merge process.

When the Service Data Objects (SDO) code runs in an IBM WebSphere Application Server environment, the performance might be impacted.

You cannot search for tasks across all pages in the

Task Manager

.

When you create a record, you face usability issues because of overlapping fields in the form.

When search strings contains accented characters, records do not appear in the search result.

When cleanse validation is configured for fields, an error message appears even though the incorrect value that was entered is corrected.

When you create records by using a custom business entity view with a default business entity, the business entity to business entity cleanse transformation does not work for lookup fields.

If an administrator rejects a task to update business entities, the records do not delete from the base object and cross reference tables.

If you log in through single sign-on (SSO), you cannot search for records.

When you use a view to business entity transformation that uses a cleanse function, the cleanse function is invoked twice.

When you filter child records by a date that does not exist in the child records, a record with a non-matching date appears.

In the search results, some rows are empty. The rows represent records that are filtered out because the user does not have permission to view the records.

When you preview a changed record from a task, the preview might not display the change bar beside some of the changed values in child records.

When a user claims a task, the task inbox does not display a confirmation message.

When Data Director populates lookup values by processing the values using a cleanse function, the following error occurs when users create a record:

SIP-14396: The unique constraint on base object was violated.

When multiple base object columns are associated with a single lookup table, search results do not appear.

After you generate a business entity schema, the Operational Reference Store validation fails.

You cannot import data in bulk.

The date fields in the

Business Entity

view,

Matching Records

view, and the

Cross-reference Records

view display the date along with the time stamp.

When you include the legacy Merge Preview in a record view, the Provisioning tool displays an error.

When cleanse validation for records fail, incorrect child record fields are highlighted.

You cannot open large hierarchies in the

Hierarchy Manager

. The application times out.

In an application server cluster environment, the changes that you make to the Data Director application synchronize across all the MDM Hub nodes.