When a search query is based on an integer field, the query does not return results.

If you log in through single sign-on (SSO) and export query results, a null pointer exception is generated.

In a record view, values that you select from dependent lookup fields do not persist.

When you delete a value in a required field and save the record with a null value, the record does not display an error message.

When Data Director is configured with a State Management Override System (SMOS) and you set the end date of a relationship in the Hierarchy Manager, the cross-reference records for all the periods are soft-deleted.

When you select a child record of a merge candidate that has one-to-many child relationship, the

SIP:50022

error is generated during the generation of the merge preview.

After a record is successfully approved in Data Director, the record state does not change from pending to active in the database. The ActiveVOS workflow fails to promote the record to the active state.

If you mark a field as read-only in a business entity, a Cleanse transformation on that field fails.

When field filters are configured for business entities, performance of the associated tasks is poor.

When you perform a search in E360 to view only active records, you can see active and pending records

If you publish a custom layout, the read-only field appears as an editable field.

In Data Director, when you update an existing record, the Save button is disabled.

When you include special characters in a query search, the search does not return any records.

You cannot update an existing column in a child record if the columns are at the business entity root level.

In an Excel sheet, if you edit data in a cell and import the Excel file to Data Director, the cell data is treated as null and does not display.

When you update a business entity, the following error message appears:

com.informatica.tools.mdm.service.entity360view.componentconfig.
ComponentConfigService: Either there is no configuration for component present 
or XML is malformed 

The Smart Search filter does not apply when you search for records.

In the

Matching Records

view, you do not have the option to select all records.

When you claim and reject an approval task, the delete pending service in ActiveVOS fails and the record is marked as dirty. This issue occurs when you set the STRIP_INCOMPLETE_IND field value to 0 in the C_REPOS_TABLE.

In Data Director, the business entity label displays a random date instead of the label name. This issue occurs when you enter a numerical value in a field that is defined with the data type as VARCHAR.

If a column is null and you want to populate the column with a unique value using the cleanse function, the column does not populate.

When you access Data Director using the HTTPS protocol, in the web debugger, the following response header tag does not appear for all URLs:

-Dstricttransportsecurity.flag

When you create a new record and select a custom date range in the Creation Date field, the following error displays: The data must be in the valid format.

Child records do not display in the History view. This issue occurs when you view parent-child records with one to many relationships.

In the Task Manager, when you attempt to filter the creation date, incorrect date numbers display.

In Data Director, when the search results contain cross reference records, child entities do not display.

When you search for cross-reference records, the Matching Records view does not display child entities.

Labels configured for business entities in the Provisioning Tool do not display in Data Director.

In the Matching Records view, child records do not merge with parent records and display the following error:

SIP-50218: Unable to run the merge process on the child. The merge process must run successfully on the parent before it can merge the child. In the merge request, add the parent records with rowids.

In the

Task Manager

, if you create a new task, it does not appear as the latest created task under

All Tasks

.

The Cross-reference Records view displays incorrect child entity label names.

Multiple functions in Data Director fail in a WebLogic 12.2.1.3 cluster environment.

In a hosted MDM environment, when you perform a query search and click the next page in the search results, a 404 error occurs.

In Data Director, when you approve a task, the records edited by the user highlight at the record level and not the field level.

When you unmerge a record with a large number of cross-reference records associated with it, the unmerge process fails.