Table of Contents

Search

  1. Introduction
  2. Multidomain MDM Version 10.3
  3. Installation and Upgrade
  4. Version 10.3

Data Director Known Limitations (10.3)

Data Director Known Limitations (10.3)

The following table describes known limitations:
Reference Number
Description
MDM-22587
When you export search results that are based on a timeline, the export process ignores the timeline and exports all data.
MDM-21988
When a user claims a task, the task inbox does not display a message to confirm that the task is not yet claimed.
MDM-21974
In a hosted MDM environment, when you log out of
Data Director
, clear the browser cache, and then refresh the tab where you logged out, a 404 error occurs.
MDM-21390
If you change your password and then run a newly claimed unmerge task, the unmerge process does not run on the records, but an interface message says that the unmerge is successful.
MDM-21388
In the task inbox on the
Home
page, you cannot filter tasks by the creation date.
MDM-21361
When you add values to dependent lookups that have no values and send the changes for approval, the approval task cannot be opened.
MDM-19053
If you use Apache HTTP Server,
Data Director
applications take a long time to load.
MDM-18712
The export of search results fails.
MDM-18260
After you create a record, you cannot edit or save the record.
Workaround: Cancel the record and then create a new record.
MDM-18259
The
getChangedChildren
method that was added to the Save Handler user exit in version 10.2 HotFix 2 is not available in this release.
MDM-18157
On Chrome, when you display the interface in Chinese, some button labels are truncated.
MDM-16761
The
deleteMovedRelInExplorerView
preference that was added in version 10.1 HotFix 5 is not available in this release.

Data Director with Business Entities

The entity views are based on business entities. To use these views, upgrade Data Director applications from subject areas to business entities.
Reference Number
Description
MDM-22817
When you filter child records by a date that does not exist in the child records, a record with a non-matching date appears.
MDM-22815
You can change the default date format used by the calendar in the Entity 360 framework.
To change the default date format, use a text editor to create a
bundleE360.properties
file that contains the property
DATE_TIME_LONG_FORMAT
. Then add the
bundleE360.properties
file to the following location:
infamdm\hub\server\resources\entityE360
If the
entityE360
directory does not exist, create the directory.
MDM-22811
In the simple merge component, when you want to change a date value, the calendar does not appear correctly.
Workaround: Type in a date.
MDM-22519
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.
Workaround: The MDM administrator has to delete the search index. From the Provisioning tool, open the business entity and add or update any searchable field. Any change to the searchable configuration deletes the index. Re-index the data for the business entity.
MDM-22369
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.
MDM-21692
The calendar controls are not localized.
MDM-18817
The
Cross Reference
page and the
Merge Preview
page have pagination issues.
MDM-18665
When you delete the Status Cd code, the following error occurs:
Cannot read property 'taskId' of undefined
Workaround: You can edit this field, but you cannot delete it.
MDM-18597
When a user role does not include the create and read privileges for a business entity, users with this role can still view the tasks associated with the business entity.
MDM-14958
In the Search box drop-down list, when the list exceeds the height of the browser window, you cannot scroll the list to see the items that are off screen.
Workaround: In the browser, switch to full screen mode. Increase the resolution until you can see the remainder of the list.
MDM-14952
In the
History
view, the timescale labels in the Options menu do not appear correctly initially.
Workaround: Interact with the timescale for the timescale labels to display correctly.
MDM-14933
In the
Hierarchy
view, business entities in the
Relationships
tab of the history do not open in Business Entity view.
Workaround: Use the Search box to find the business entity, and then open the entity in a Business Entity view.
MDM-14932
In the
Timeline
view, you cannot open the relationship records that appear on the
Relationships
tab.
MDM-14920
In the
Hierarchy
view, in the Entity Details dialog box, when you click
More Details
, the dialog box closes without opening the selected business entity.
Workaround: Use the Search box to find the business entity, and then open the entity in a Business Entity view.
MDM-14919
In the
Hierarchy
view, the anchor entity
Actions
Open in New Tab
option does not open a new tab.
MDM-14918
In the
Hierarchy
view, the anchor entity
Actions
Edit
Edit Entity
option does not open the business entity.
Workaround: From the View list, select the Business Entity view.
MDM-14890
In Microsoft Internet Explorer 10, the
Log Out
button is not visible from the Business Entity view and details do not display correctly in the History view.
Workaround: Use another supported browser.
MDM-14781
In the
Matching Records
view, when you select a child record as the target record, the interface lets you select a record in the pending state. However, pending records cannot participate in a merge process, which means that the merge fails.
Workaround: Select a child record in the active state as the target record.
MDM-14460
If the time zone of the application server is different from the time zone of the client, the time of an event in the History view differs from the time in the event details panel.
MDM-14385
When you view the details of merge and unmerge operations, user names are sometimes prefixed with
e360
in the Updated By or Created By fields.
MDM-14327
If there are multiple pages of search results for business entity child records and you type in a page number beyond the range of pages displayed, subsequent attempts to view a page of search results fail and an error occurs.
MDM-11397
If you use the mdm_sample Operational Reference Store, you cannot add or update the phone number of a Person business entity.
Workaround: Before you add or update the phone number of a Person business entity, perform the following steps:
  1. In the Hub Console, start the
    Cleanse Functions
    tool, and then acquire a write lock.
  2. Click
    Custom
    Parse Phone Number - NA
    .
  3. Click the
    Details
    tab of the Parse Phone Number - NA function.
  4. Right-click on
    Condition
    and click
    Edit Condition
    .
  5. In the
    Edit Condition
    dialog box, for each case value, change the country code from
    +1
    to
    1
    .
  6. Save the changes and use the Repository Manager to validate the metadata.
MDM-8768
After you upgrade and then delete all the configuration files from the repository table c_repos_component_instance, tasks might not display in the Task Manager inbox for the first user who logs in to Informatica Data Director.
Workaround: Log out of Informatica Data Director and then log in again.
MDM-8764
When you generate the business entity schema from a subject area configuration, mandatory lookup fields are not included in the business entity view configuration or transformation configuration.
Workaround: In the Provisioning tool, add the missing configuration code:
  1. Select
    Advance Configuration
    Business Entity Views (XML)
    .
  2. Add the following code to the lookup configuration:
    <ns2:field name="<
    missing field name
    >"/>
  3. Select
    Advance Configuration
    Transformation Configuration (XML)
    .
  4. Add the following code to the co2view configuration:
    <input name=”<
    missing field name
    >” field=”<
    missing field name
    >”/> <output name=”<
    missing field name
    >” field=”<
    missing field name
    >”/>
  5. Add the following code to the view2co configuration:
    <input name=”<
    missing field name
    >” field=”<
    missing field name
    >”/> <output name=”<
    missing field name
    >” field=”<
    missing field name
    >”/>
  6. Select
    Advance Configuration
    Business Entities (XML)
    .
  7. Add the following code to the lookup configuration:
    <ns2:field name="<missing field name>" label="<missing field name>" column="<missingcolumn name>" required="true"/>
  8. Click
    Update
    .
  9. Click
    Validate + Publish
    .
MDM-8606
In the
Matching Records
view, when you merge records, the system can appear unresponsive.
Workaround: Wait until the merge job finishes.
MDM-7597
If you delete a record and then search for the record, the ROWID of the deleted record still displays.
MDM-5715
On Internet Explorer 9 and 10, if you group search results by type, you cannot then expand the search results.
Workaround: Use Internet Explorer 11 or alternative browsers such as Chrome, Safari, or Firefox.
MDM-5333
Match and merge is not supported for business entity child records. If you try to add match records to a child record, you might corrupt the data.
MDM-4710
In the
Business Entity
view, when you add data to a business entity and then click
Apply
, the Hub Server does not clean and correctly format the data.
Workaround: For your data to appear in the correct format in Business Entity view, click the
Save
button.
MDM-2699
In calendars, you cannot set a date before January 1, 1000.
MDM-2584
In the
Task Manager
, you are unable to sort tasks by Task ID, Task Type or Task Status.
MDM-2574
In the task inbox, setting the Owner filter to
Unclaimed
does not return the list of unclaimed tasks.

Data Director with Subject Areas

The legacy views are based on subject areas.
Reference Number
Description
MDM-21793
When you create a record, potential matches do not appear.
MDM-21427
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-19980
In the
XREF
view, the search runs with administrator privileges instead of the logged in user privileges.
Workaround: Increase the ULIMIT.
MDM-19608
In all the data views, white space is not preserved in the data fields.
MDM-19421
If you exceed the maximum length of a text field, no validation error is displayed.
MDM-18915
When an exact match rule includes columns from child records, the Find Duplicates operation returns child records that do not match.
MDM-18854
In the
History
view, when you try to view an event detail, an error might occur.
MDM-18680
In applications with multiple subject areas, tasks assigned to a user do not appear in the task inbox.
MDM-18632
When you run a search query with a specified effective date, the search results display incorrect values for records from a child subject area.
MDM-18442
When lookup columns from a child table are included in an advanced search query, the search result does not contain the values of the lookup field from the child table.
MDM-18163
You cannot use a custom profile or multithreading to export search results.
MDM-16464
When you run a search query with a specified effective date, the search results display incorrect values for records from a child subject area.
MDM-14872
In the
Matches
view, users can add a record as a merge candidate that has already been selected to merge with another record. When the record is added as a merge candidate, an error occurs.
MDM-13787
In the
XREF
view, you can select a cross-reference record to unmerge when an unmerge task already exists for that record. An error occurs when the duplicate unmerge task is processed.
MDM-10613
In the
Hierarchy
view, when you end date a relationship and the relationship record is from a different source system than the IDD SMOS system, the existing relationship record is deleted.
MDM-9796
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.

0 COMMENTS

We’d like to hear from you!