Release Notes

Back Next

Informatica Data Director Fixed Limitations

The following table describes fixed limitations:

Reference Number	Description
MDM-13920	When you log into an IDD application with a Korean user name, the login fails with an exception.
MDM-13625	If you use a custom login provider module to log in to Informatica Data Director, the main page does not display correctly.
MDM-13453	If you have multiple Informatica Data Director applications that use different subject area names for the same Operational Reference Store, a null pointer exception occurs when you log in.
MDM-13452	If you use a custom login provider module to log in to Informatica Data Director, the main page does not display correctly.
MDM-13119	In the Data view, the Relationship section for an entity might not expand, and the following error appears: "ORA-12704: character set mismatch for GET ONEHOP"
MDM-13110	You cannot clear a dropdown value that you selected.
MDM-12943	When using the ReadCO service on a business entity, a GET request fails if the text in the field contains a dollar sign ($).
MDM-12874	When you click Change Language and select a locale, the text in the user interface does not change.
MDM-12700	When you load tasks in IDD, the process might fail with the following error: SIP-10324: Unable to close down JDBC objects opened for query
MDM-12692	If you have ActiveVOS configured in the MDM Hub environment, in IDD, a merge task might fail to merge records.
MDM-12516	When you update a record for an entity that was created in another source, Informatica Data Director creates a cross-reference record with empty effective dates.
MDM-12211	The import of an Informatica Data Director application to another environment fails when the application is in a ZIP file.
MDM-12013	When you move the pointer over a record that contains an apostrophe, the original and merged values do not appear in the merge preview.
MDM-11862	From the legacy Matches view, if you open a merge candidate in the Data view, make a change, save, and then return to the Matches view, the merge candidate does not always show the latest data. The replacement Matching Records view does not permit you to open a merge candidate to change. Changes to merge candidates from other IDD instances are reflected in the view.
MDM-11392	If you open a task pending approval, in the dependent lookup value of the child lookup column, the description of the original value appears as code.
MDM-11282	When you update a record and select the XREF view, the following error message appears: Cross references not found for the current master record.
MDM-11152	In the Hierarchy view, when you disable an entity type in the Filters tab, you cannot create relationships with those entities. Workaround: Before you create relationships, open the Filters tab, and select the entity types that you want to use in the relationship.
MDM-11087	When you log in to Informatica Data Directory and bookmark the redirected URL in a browser, the bookmarked URL does not open Informatica Data Director.
MDM-11085	If LDAP authentication is enabled, you can log in to Informatica Data Director, but your user name does not display in the upper-right corner of the page.
MDM-11083	When you update a pending ActiveVOS task record, Informatica Data Director does not preserve the pending state when it applies the changes.
MDM-11077	When you save a subject area record at the same time as another user, you might get an error.
MDM-11002	In the Potential Matches area, when the number of matched records exceeds the page size, the remaining matched records appear on additional pages. When you sort the matched records, the matched records on the visible page are sorted, but the matched records on the other pages disappear.
MDM-10950	When you create a task for a record that has cross-reference records from more than one source system, a null pointer exception is generated.
MDM-10867	When you log in with user credentials that are not valid, a blank page appears.
MDM-10866	After you localize lookup tables to support multiple languages, the values in some drop-down lists do not reflect the selected locale.
MDM-10801	The Data Security filter does not work properly on child match path columns.
MDM-10686	When you update a record for an entity that was created in another source, Informatica Data Director creates a cross-reference record with empty effective dates.
MDM-10637	You can search for records that contain Turkish characters.
MDM-10629	When you create a task for a record that has cross-reference records from more than one source system, a null pointer exception is generated.
MDM-10626	In the Hierarchy view, the history of a record does not display as expected.
MDM-10616	If you add a relationship type to hierarchies in a Microsoft SQL Server environment, Informatica Data Director does not add the relationship type to the Metadatabundle.properties file.
MDM-10543	If you edit a parent record, and then click the Cancel button, grandchild records of the parent record do not retain their read-only status.
MDM-10528	It takes longer than expected to open a merge task.
MDM-10524	Dependent lookup does not work for saved search queries.
MDM-10523	When you update a timeline-enabled parent record in a subject area, and if a child record that is not timeline-enabled in turn has a child record that is marked for update, the IDD application fails. An IndexOutOfBounds error is generated.
MDM-10323	When the metadata for an Operational Reference Store is not valid, Informatica Data Director does not display the list of deployed applications. Applications that use a different, valid Operational Reference Store are also unavailable. To show the list of deployed applications, edit the cmxserver.properties file and add the following property: cmx.display.deployed.invalid.met.app=true
MDM-10295	You can import data into a lookup table with INT values as keys. When the import process encounters an integer value greater than 2³², the process generates a java.lang.NumberFormatException error.
MDM-10272	Some validation error messages identify subject areas by the name instead of the display name. The issue occurs for subject area child records with the relationship type Part of Primary.
MDM-10120	When you create a record, the one-to-one child subject area for the record is blank and you cannot see the one-to-one child values in Matches view.
MDM-10098	In the Data view, some required fields are not enforced. This issue occurs when the required fields belong to subject area child records with the relationship type Part of Primary .
MDM-10097	The Hub Server properties http-only and cookie-secure do not work in Informatica MDM Multidomain Edition 9.7.1 and later.
MDM-10074	You can include child records in search results by enabling the includeChildrenToSearchResults property. If you open a record from the search results and then update the parent record, when you return to the search results tab, the values for the child records do not appear.
MDM-10073	When the data type is NUMBER(15,8), Informatica Data Director displays a zero value as 0E8 instead of 0 .
MDM-10059	When you update the effective period of a record, some columns might be saved with the NULL value.
MDM-10058	You cannot create and save data for a new effective period. The following error is generated: SIP-10165: Input value is required for column: ROWID_OBJECT.
MDM-10056	In the History view, subject area child records are identified by the name instead of the display name.
MDM-10053	When you save a query, the save process fails with an error. This issue occurs when the query references a record that is related to the base object record by the Part Of relationship type.
MDM-10051	When you open a child XREF tab, no information appears.
MDM-10049	The first time you log in to Informatica Data Director, the log in process takes longer than expected.
MDM-10045	In WebLogic environments, when Informatica Data Director redirects a user to the login page, a blank page appears instead of the login page.
MDM-10041	When history is enabled on base objects and you use the GET Package API to query the base object, the query fails with a data access error. This issue is related to the shadow columns that were added to improve traceability between child and parent cross-reference records (MDM-3492).
MDM-10035	When you edit and save the effective period for a record, the following error is generated: 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.
MDM-10030	When multiple grandchild records access the same base object through different match paths, you cannot view the details of an associated task.
MDM-9974	After you install Informatica MDM MDE version 10 HotFix 2 EBF 6, a user cannot claim or open a task.
MDM-9955	When the metadata for an Operational Reference Store is not valid, Informatica Data Director does not display the list of deployed applications. Applications that use a different, valid Operational Reference Store are also unavailable. Fix : To show the list of deployed applications, edit the cmxserver.properties file and add the following property: cmx.display.deployed.invalid.met.app=true
MDM-9821	For a base object that has timeline enabled, you cannot create a relationship with a future date or past date.
MDM-9818	The history view in Hierarchy Manager does not work as expected. For a base object that has timeline enabled, you cannot create a relationship with a future date or past date.
MDM-9798	In the Hierarchy view, when you view the event details of the relationship history of a record, an error occurs.
MDM-9622	If a child foreign key in a search query has a specific option, the searchQuery API returns incorrect search results.
MDM-9620	When you perform a full export of the data from the Search Results page, some fields are missing. The missing fields belong to subject area child records with the relationship type Part of Primary .
MDM-9615	When you create a task from the Search Results page, you do not see a confirmation message that the task was created successfully.
MDM-9612	In the History view, subject area child records are identified by the name instead of the display name.
MDM-9608	After you send a task for approval, a warning message states that you will not see the new record due to the security filters. After the task is approved, you can see the record.
MDM-9606	When you open a child XREF tab, no information appears.
MDM-9556	When user names contain uppercase letters, the task inbox does not show the tasks for these users.
MDM-9554	When you log in to Informatica Data Director with external authentication, the task inbox does not contain pending tasks and the logs contain a NullPointerException error.
MDM-9551	In WebLogic environments, when Informatica Data Director redirects a user to the login page, a blank page appears instead of the login page.
MDM-9490	After you use a REST API to add an effective period to an entity that is enabled for Hierarchy Manager, the cross-reference table does not contain the specified period start date and end date.
MDM-9440	When a parent record has multiple child or grandchild records and you update one of the child or grandchild records, the save process takes longer than expected.
MDM-9391	In the XREF view, the fields for subject area child records with the relationship type Part Of Primary do not appear.
MDM-9388	In the search fields, a drop-down list is empty. The lookup column containing the fields is in a subject area child record with the relationship type Part of Primary .
MDM-9383	When you change the effective date of a child record, Informatica Data Director applies the same effective date to the parent record.
MDM-9365	When a reviewer edits data and approves a task, the Comments dialog box appears before the validation process runs. The issue occurs when a user exit handles tasks.
MDM-9213	When you create business entities as an external user and send for approval, Informatica Data Director does not create review tasks for the business entities. The issue occurs if the MDM Hub uses the ActiveVOS Server as the default workflow engine and an external user profile provider to manage user profiles.
MDM-9196	For each insert or update, more than one message is published on the message queue.
MDM-9179	Custom queries that contain greater than 4,000 characters cause the searchQuery API to fail with a syntax error.
MDM-8866	In the Hierarchy Manager, when you create a relationship and then end the relationship, the following error is generated: SIP-10321: Error updating relationship record
MDM-8854	When history is enabled on base objects and you use the GET Package API to query the base object, the query fails with a data access error. This issue is related to the shadow columns that were added to improve traceability between child and parent cross-reference records (MDM-3492).
MDM-8846	You can include child records in search results by enabling the includeChildrenToSearchResults property. If you open a record from the search results and then update the parent record, when you return to the search results tab, the values for the child records do not appear.
MDM-8838	When you select an unopened record in a grandchild subject area, the load process runs. If you click the Add button while the record is loading, a NullPointerException error is generated.
MDM-8836	When the data type is NUMBER(15,8), Informatica Data Director displays a zero value as 0E8 instead of 0 .
MDM-8833	In the Hierarchy Manager, when you click Get One Hop , the following error is generated: SIP-10324: The data types nvarchar and datetime2 are incompatible in the add operator. This issue occurs when the entity label uses the date column.
MDM-8761	When you update the effective period, the following error is generated: SIP-40608: Cannot update the effective period. The start date or end date is not valid. This issue occurs when a cross-reference record contains null values for the start date and the end date.
MDM-8759	The search results might contain incorrect values because of conflicts between the ROWID_OBJECT and ROWID_XREF values.
MDM-8736	In the XREF view, the values for the trust-enabled columns of a record are incorrect.
MDM-8683	When you update the effective period of a record, some columns might be saved with the NULL value.
MDM-8681	You cannot create and save data for a new effective period. The following error is generated: SIP-10165: Input value is required for column: ROWID_OBJECT.
MDM-8680	When you update a timeline-enabled parent record in a subject area, and if a child record that is not timeline-enabled in turn has a child record that is marked for update, the IDD application fails. An IndexOutOfBounds error is generated.
MDM-8642	When you edit and save the effective period for a record, the following error is generated: 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.
MDM-8533	In the Hierarchy view, when you select Actions History View , select a base object update event, and then click View Event Details , the application crashes.
MDM-7190	You can edit a child record and a grandchild record at the same time. If you apply the edit to the grandchild record, but cancel the edit for the child record, a NullPointerException is generated.
MDM-7173	In the History view, the wrong event details are displayed for lookups when the base object record row ID is different than the cross-reference record row ID.
MDM-5639 HORA-46448	When changes to effective dates are not contiguous with the original effective dates, the Mark for Save action fails.
MDM-5577	If you use the Promote API but do not provide a source key, the MDM Hub runs an SQL statement that results in a full table scan. Consequently, performance becomes slower.
MDM-805	When you perform Informatica platform staging and there is more than one Operational Reference Store registered in the Hub Console, metadata might be inaccurate. Updates to staging table metadata are inaccurate if there are base objects with the same name in different Operational Reference Stores.

Rename Saved Search

Table of Contents

Release Notes

Release Notes

Informatica Data Director Fixed Limitations