Child records added by an external call are not visible in Data Director until you save the parent record.

When you log in to Data Director, you can see the business entities available to the previously logged in user, even when your user account is not authorized to access these business entities. This happens because Data Director does not cache all operations at the user level.

When you try to import data, you might get the following error message:

User interface components do not scale correctly. The components are squished and do not take up the entire screen area.

Data Director cannot filter dependent lookup fields that contain special Unicode characters.

When the search or list operations return a significant amount of data, for example, more than 100 records, and localization is enabled in the Provisioning Tool, the search results take a long time to load.

When the field named Status exists in a child record, it interferes with the

navCtrl.getStatus(node)

command and prevents correct navigation through the following screens:

Data Director with subject areas:
History, Effective Periods
Data Director with business entity views:
History, Timeline, XREF, Merge

When you click the child record in these screens, the record data does not appear in the right-side pane.

In the

Merge Preview

screen, dates are not rendered correctly. For example, in the Provisioning Tool, configure the

Default Display Formats

to use

yyyy-mm-dd

. In Data Director, open the

Merge Preview

screen. The previous and not the current date appears. For example, 2020-12-23 instead of 2020-12-24.

When you modify a child business entity and save the changes, the parameter

cmx.e360.submit_all

incorrectly replaces some changed field values with the original values, if set to

true

in the

cmx.serverproperties

file.

When you modify the constraints of a business entity relationship defined in Hierarchy Manager, the business object record that represents the target relationship is deleted and a new record created. This causes the unique constraint violation error if the business object relationship contains a unique column in the relationship table.

When you export a large number of records from a business entity view that contains multiple lookup fields, the export takes longer than expected.

When you save business entities that reference each other as reference lookups, an error in persisting occurs.

Localized interface does not appear correctly when you launch Data Director in Microsoft Internet Explorer Version 11.

Pending OneToOne child candidates for promotion to the Active status do not appear in Data Director. As a result, you cannot promote them to the Active status.

When you log out of a Data Director session, the session remains available. You can click the application screen to bring up a dialog box stating that the session has expired, and then on the X icon in this dialog box, to continue working in the application.

The cleanse validation function applies only if one of the fields contained in the function and mapped in the BE2B transformation is updated.

When you hover over a child record with a lengthy name, and then move the mouse out of focus, the entity name does not always disappear. Instead, it remains displayed.

When you edit a field value and save the record, the cleanse transformation associated with an unedited field value fails.

A user belonging to a user group does not have the same privileges of a user who belong to the same user role assigned to the user group.

When you open a merge task, it takes a longer time to open.

When you use the Form view to add or edit a child record, the data is not cleansed and standardized.

When you run a Tokenize job, the job fails and you get the following error message:

When you edit and save a record in the Business Entity tab, as an administrative user, the Person Dashboard is incorrectly highlighted even though the Business Entity tab where you edited the record remains displayed. The selected tab and the context view should be the same.