In the Hierarchy Manager view, the direction of the arrow appears incorrectly for child records.

When you create a record, if the parent lookup values contain the pipeline (|) character, the dependent lookup values do not appear.

When you open a merge task with a cyclical business objects configuration, the following error appears:

Caused by: java.lang.UnsupportedOperationException 
at java.util.Collections$UnmodifiableCollection.addAll(Collections.java:1067).

When you update one or more fields and the value populates to a read-only field based on the transformation rule, the following error appears:

SIP-50022: Validation failed. The field is a read-only field. In the request, do not change the value for this field.

The Query tab takes longer than expected time to load the saved queries.

When you import a file that contains more than 100000 records, the file import process does not work as expected.

When you change the effective date value of a record, the record displays an incorrect value in the XREF view.

When you use multiple Record Details components in a page layout and save the record, a confirmation message displays that an incorrect field was updated.

In the Legacy view, if you have a pending review task for a child record update, the

Save

button is disabled.

When you use the Similar Records component to search for records, the results display only root records but no child records.

After you upgrade to Multidomain MDM 10.4 and you use the Siperian workflow adapter, the previously created tasks do not appear on the Tasks tab.

In the Home page, when you open a task, the Task Manager page displays the following error message:

internal server error

.

In the Siperian workflow based Task Manager, when you approve a task, the task page might refresh without any change in the task workflow or the following error message displays:

com.informatica.mdm.cs.server.CompositeServiceInvoker: Error in service execution

java.lang.NullPointerException

When you open a record in the Data View and edit the date in the Effective Period field, the following error message displays:

com.siperian.dsapp.jsf.server.DSUIServlet: Uncaught error java.lang.NullPointerException

When you perform a cleanse transformation, the cleanse function is triggered with missing input parameters and the results might display incorrect values.

When you edit a record and switch the layout to view the record, the original value displays. The edited valued might not display.

When you update the Lookup field with one-to-many relationships, the update may fail and displays an error message.

When you re-import a file with records into Data Director, the XREF records might display null values.

When you query merged records, the results may display incorrect records when you compare and view the same merged records in the Merge Preview view.

After you merge two records using task actions, the consolidation indicator is set to 2 instead of 1.

In an Oracle Weblogic environment, when users access Data Director using an HTTP URL, the Available Tasks window might not display any data.

If a field has an invalid value and you run a cleanse validation process, the following error message might display:

SIP-50022: Validation failed.

When you create a task, the automatic task assignment daemon does not assign a task to the user in the task assignment table.

The History view might displays the foreign key value of the record instead of the field display value.

If you update multiple child records of a business entity, all records might not get updated.

When you create a record and select a previously added child record while adding a second child record, the details of the first child duplicates and overrides the details of the second child.

In Task Manager, users can edit tasks after the task is approved.

When you attempt to view cross reference records outside the specified effective date, the records might display an incorrect value in the XREF view.

In the History view, the records are compressed and might display with a scroll bar.

When you run a query with filters, an error message appears.