When you use the bulk import operation to associate a technical data element to multiple glossaries and assign a business name and description, the glossaries are not associated and the business name or description is not assigned to the technical data element.

If you import a technical data element sheet that contains duplicate business data set names, the data elements of the duplicate data sets get associated with each other. This results in an incorrect hierarchy of the data elements.

When you perform case insensitive connection assignment for catalog sources, the unmatched reference objects display incorrect hierarchy.

When you export search results containing Informatica Data Management Cloud assets, the exported file does not include those assets.

The preview job for failed rows for a Snowflake catalog source displays truncated results for the timestamp field.

When you extract metadata from an Informatica Intelligent Could Services catalog source, the mappings and mapping tasks show incorrect hierarchy if they are are located in different projects.

Microsoft Power BI data sets in the catalog may display duplicate entries for fields. This issue occurs when the Microsoft Power BI columns contain a period in their names.

When you extract metadata from a Google Looker catalog source, the value for the Google Looker system attribute

Native ID

is not displayed in the catalog.

You cannot view complete data lineage for the assets in the IBM Cognos catalog source if the MySQL queries in the IBM Cognos source system are converted to UTF-8.

The data profiling job for Amazon Redshift source systems completes successfully in

Metadata Command Center

but the profiling results for views are not visible in

Data Governance and Catalog

.

The bulk import job for technical assets fails if the

Lifecycle

field in the bulk import file is left blank.

When a custom workflow for an asset is configured with a human task that has only one action, then the workflow stakeholders cannot perform ticket-level operations for those assets in

Data Governance and Catalog

.

When the data quality rule is run successfully, you cannot preview the failed rows for the rule occurrence if your

Data Governance and Catalog

tenant is on the April 2024 version and the Metadata Platform Service is on the May 2024 version.

You cannot delete a schedule for a data quality rule occurrence in

Administrator

even if you delete the frequency attached to the rule occurrence in

Data Governance and Catalog

.

When you update the description of a data set by pasting text from external applications, the description displays junk HTML codes when you view it from the widget on the

Home

page.

When you enter a default date for a custom attribute in

Metadata Command Center

, the default date changes as per the browser timezone when you create an asset in

Data Governance and Catalog

.

The lineage is not extracted properly from the QlikSense Cloud source system if the alias name of the column is passed in the query.

If

Metadata Command Center

extracts metadata for a Tableau dashboard that contains commas in its name, multiple Tableau dashboard assets are created in

Data Governance and Catalog

for a single dashboard asset.

If a QlikSense source system that contains tables with the same names inside different projects, the lineage is not extracted properly in

Data Governance and Catalog

.

You cannot create or delete a stakeholder for data quality rule occurrences using the Stakeholder template for bulk import.

When you search using the following queries, the search times out:

folder containing folder <folder name>
folder containing file <file name>
tables related to column <column name>

If you create duplicate relationships between assets in the relationship sheet, the bulk import job fails without an error.

The hover text for the catalog source types in the search filter displays a JavaScript error.

The bulk import job for assets fail if the import file contains Japanese characters.

When you search among the child assets of an asset from the Browse page, the search times out.

The bulk export file contains duplicate records of some assets.

If you delete the relationship between a data element that is linked to a Data Quality rule occurrence as its primary data element, the primary data element is removed from the Data Quality Rule Occurrence.

The bulk import job for assets fail if the column name contains a special character.

When a series of data observability jobs run on a source system, the sixth job fails.

The job

Overview

page for a data observability task marks the status of the job as 'Completed' while the status of the bulk ingestion subtask remains in the 'Submitted' state.

The bulk import job fails with an error when a data element classification and a generated classification are created with the same name.

In some situations, the lifecycle status of assets and open tickets does not get updated for Business Term assets that are created using the bulk import process.

If you do a prefix search, the results are not accurately returned.

Some special characters are not displayed correctly in the

Resolution

section of a ticket.

If an asset is in the

Draft

state and no workflow is associated with this asset, the

Send for Approval

button is visible. However, you cannot publish the asset.

If you bulk export more than 10,000 assets for a catalog source, it exceeds the limit and as a result the data is not displayed correctly in the bulk export sheet.

If you have more than 20 stakeholders, the number of stakeholders is incorrectly shown in the

Stakeholder

tab of an asset.

Data Governance and Catalog

consumption reporting application was not available for five days. As a result, the Informatica Processing Unit (IPU) consumption was incorrectly displayed.

If a user is part of a user group, the user does not inherit privileges for roles that are assigned to the user group.

You cannot delete more than three data element classifications at the same time.

Bulk export process fails when invalid characters are present in the custom attributes of assets.

In the

Ticket Manager

page, if a ticket is due on a particular date, the overdue tasks for that ticket incorrectly appears as zero on the due date.

When you delete a catalog source in

Metadata Command Center

, the catalog source is deleted from

Metadata Command Center

, but the assets associated with this catalog source are still present in

Data Governance and Catalog

.

The

Ticket Manager

page does not display the role of the current task owner.

In the

Ticket Manager

page, if a ticket is due on a particular date, the overdue tasks for that ticket is incorrectly displayed as zero on the due date.

If the workflow inbox is opened before you open a new task from the notification panel, the previously opened task is still selected in the workflow inbox.

You can perform a metadata extraction for Informatica Intelligent Cloud Services catalog source even when the Informatica Intelligent Cloud Services license is not available.

The data lineage for Informatica Intelligent Cloud Services mapping that uses source SQL query does not display all the tables.

When you perform a metadata extraction of Informatica Intelligent Cloud Services after connection assignment with Microsoft Azure Synapse in

Metadata Command Center

, the schemas that you observe in the data lineage of

Data Governance and Catalog

are incorrect.

When you trigger a job in Metadata Command Center that performs metadata extraction from Microsoft Power BI, data lineage is not available for this catalog source as

null

is present instead of

options

in the

PowerQuery AzureStorage.DataLake

function.

When you trigger a job in

Metadata Command Center

that extracts metadata from Microsoft Power BI, the data lineage is not available for this catalog source as improper URLs are present in the

PowerQuery AzureStorage.DataLake

function.

If you create a data set with more than 200 data elements in

Data Governance and Catalog

and then expand the data set of a related System asset in the

Hierarchy

tab, the data elements of the related System asset are not displayed.

When you return a ticket of an ongoing workflow, the

Workflow Assigned to You

notification is sent to stakeholders of other human tasks.

When you associate more than 2000 assets with a data element classification, the

Associations

tab of the data element classifications displays only 2000 associated assets.

Data element level lineage is not visible for a data flow table that is created with the SAP HANA source system.

For Google Big Query catalog source, the

Code

tab is not visible for Data Governance and Catalog when a table is created with the STRUCT data type.

Data Integration

Salesforce Connector doesn’t include a toolkit implementation.

For the request token, users do not get data set parameters and face parsing issues.

When you export 10,000 or more asset types to a local file, the asset types do not display correctly in the exported file.

You can export the lineage information of an asset from

Data Governance and Catalog

even if the Export feature is not enabled for your user role.

A user with the super admin privilege is unable to delete the stakeholder for an inactive user or user role.

The data quality score status is incorrectly displayed as Acceptable for a target value of 100 and a threshold value greater than 99 even when the data quality score is 100% for a data quality rule occurrence.

Suppose you use a Data Quality rule specification to create a rule occurrence in

Data Governance and Catalog

and later change the rule specification in Data Quality. In that case, the updated rule specification does not appear in the

Technical Description

field of the data quality rule occurrence

Overview

page of

Data Governance and Catalog

.

You can create more than one business asset with the same name without seeing any warning message.

When you update the custom attribute values in the Technical Data Source sheet in the bulk export Microsoft Excel file, the re-import of the exported file fails with an error.

When you rename a user group in Administrator and export assets with this user group as a stakeholder, the exported file does not reflect the renamed user group.

If you do not have permissions to access a particular data profile, you cannot click the

Profile Reference

link in the rule occurrence that is linked with the data profile.

When you click the

Notification

icon to view the open items, the

Unread

count is not displayed correctly after you click any open item.

If you create assets A and B and assign asset A as the parent of asset B, you can assign parent B as the parent of asset A.

If users A and B are added as stakeholders for an asset and the email notification setting is disabled for the users in the

Settings

page, the users A and B do not receive notification emails. If you add multiple users as stakeholders to an asset, only the user for whom the email notification is enabled in the

Settings

page will receive the notification emails.

In the bulk export Microsoft Excel file containing search results, when you update the

Description

field in the Technical Data Source sheet, the re-import of the exported file fails with an error.

When you upgrade to the current release, and re-run the catalog source job, data lineage information is missing for few assets of SAP BusinessObjects catalog source.

If a single connection has several different endpoints and you assign connections to the end points, the assignment job might take a long time to complete. For instance, if a single connection has 50 different end points and you want to assign 50 connections, the job can take more than 15 hours to complete.

The status of a ticket with the workflow changes from

Open

to

Resolved

when the stakeholder of the ticket approves it. But, the status of the asset lifecycle does not change to

Published

. This is because the stakeholder of the asset does not have the permission to update the asset.

When you import assets in the catalog using bulk import, the timestamps on the

Overview

and

History

tabs do not match.

The data quality rule occurrences do not propagate from a child system to a parent system if the systems are in a parent-child relationship.

If you create a subdomain using bulk import and you update the reference ID of the subdomain in

Data Governance and Catalog

, and then add the name of the subdomain as the parent while creating a business term using the bulk import template file, the newly created business term in

Data Governance and Catalog

does not display the correct subdomain.

When you open an asset B from the

Lineage

tab of the asset A, the

Overview

tab of asset B opens. You need to manually navigate to the

Lineage

tab of asset B.

If two assets are in a parent-child relationship, you cannot delete the parent asset.

When you download an exported file containing results of a search in the Microsoft Excel format, the

<p>

and

</p>

tags are added for single lines in the

Description

column for the glossary terms in the bulk export file.

If you want to modify either the business name or the description for a data set or data element and do not specify values in both the fields, the values for either of the fields disappear after you save the business term.

When you create a system and do not specify any data sets for the system, the

Lineage

tab of the system displays an error.

Norwegian characters do not appear correctly when you run the data profiling job on a Windows agent.

If a system asset is not associated with any data set, then the

Lineage

tab of the system displays an error.

In the bulk import file, when you associate an asset A with a parent asset B, and you update the parent of asset B, and then run the bulk import process, the asset details page for asset A does not display the correct hierarchy for parent assets on the top of the page.

When you perform connection assignment to view data lineage for Microsoft Power BI assets that connect to SSAS assets, you may observe duplicate assets in the lineage as both reference objects and actual connections are displayed in the lineage.