The last name of LDAP users appears twice in the Informatica Administrator, Enterprise Data Catalog, and the Catalog Administrator.

Scanning fails when a job name in the DataStage project consists of more than 60 characters.

In the Advanced Scanners application, in the Connection Registry section, there is no vertical scroll bar. You can see only 10 database entries for a host.

Users authenticated using SAML SSO are prompted to log in to Enterprise Data Catalog for each Catalog search.

When you use an Informatica Axon resource to extract objects from Axon 7.1, the parent name for the SAP HANA Attribute type does not appear.

When you run a profile on multiple resources in the high-priority mode, the profile jobs fail to fetch the profile results of a few resources.

The Business Glossary resource fails to extract the category attribute from the data source.

When you access a tabular asset and filter the columns from the Columns tab, the expected columns are not returned.

You cannot view the Salesforce objects in the Relationship tab for a data domain.

A non-administrator user cannot view the value frequency results of a Snowflake resource in Enterprise Data Catalog.

For custom attribute values of type

Classifications

and

Business Terms

, the

Select

window does not display any business terms when the

Show active buisness term

option is enabled.

Enterprise Data Catalog Plug-in does not display assets in the

Related Technical Assets

and

Classified Assets

sections of an Axon Glossary and Business Glossary term

Overview

tab.

In Enterprise Data Catalog version 10.4.1.2, you lose the enrichments configured for the Tableau resource when you run the resource again.

If you run an IBM DB2 resource that contains tables of LONG VARCHAR datatype, the resource fails.

When a large number of tasks are loaded in the Monitoring workspace for each resource scan job, the Catalog Administrator hangs.

When you configure an Amazon Redshift resource with the

First N rows

or

Random N rows

option, the profile job fails for the resource.

The data provisioning task fails for the following source connections:

Amazon S3
Azure Data Warehouse
Teradata
JDBC Oracle
Amazon Redshift
Azure Blob
Salesforce

The data provisioning task fails for the following target connections:

Amazon S3
Azure Data Warehouse
Teradata
JDBC Oracle
QlikView

When editing a resource, certain schedules display a blank name in the Schedule tab. Also, after scheduling the job, the job name is displayed as undefined.

The SAP S/4HANA resource does not extract metadata from the SAP S/4HANA application components and packages if the application components and packages have the same name.

Purging a resource takes a longer duration compared to purging a resource in version 10.4.0. This is due to additional consistency checks performed to improve catalog stability.

You cannot view sections such as Questions, Reviews, and Ratings for a Process Definition in the Catalog.

When a user who follows an asset is deleted, unexpected error messages are generated in the domain log.

The rejected data domains still appear in the inferred state even after you delete the rejected data domains from the import file during the asset data import.

The custom attributes that you have selected do not appear when you upgrade from an earlier version.

Custom attributes that contained hierarchy does not appear in a hierarchical order.

For a tabular asset in the Columns tab, the Business Title column contains incorrect values.

If you create views using the DDL script, a profiling job fails for views in an Amazon Redshift resource.

When you run a resource that contains greater than 255 characters in the source file path, a profile job fails with the following error message:

"]ORA-12899: value too large for column "C02647306"."IDP_RESOURCE_VIEW"."PROPERTY6" (actual: 349, maximum: 255)"

When you log in to Enterprise Data Catalog as an LDAP user, you cannot view objects of type primary key constraint.

When editing an asset description, if you click on Cancel, the original description is deleted.

Erwin Entity is linked to Teradata Table using logical name instead of physical name.

Users who have been assigned as the data owners for a reference resource do not get the permissions for that resource.

When you export a resource, the custom attribute values such as the Department, Data Owner, Data Steward, and Subject Matter Experts propagated to a table or column from a resource do not get added to the exported file.

When you run a profile on the Microsoft SQL Server Database resource, the profiling job skips columns that are of custom datatypes nvarchar(max) and varchar(max). This issue occurs if you specify the ODBC as the source connection type on the

Metadata Load Settings

page.

After you import the .csv file that contains business term association into the catalog using the resource import option, you cannot view the business terms associated with columns that belong to multiple tables in a resource.

When you attempt to create a table containing Cyrillic characters with links to objects in the Axon glossary, an error occurs.

The resources whose description contains more than 255 characters do not appear in the

Library

workspace.

Data Asset Analytics displays incorrect active users count in the

User Adoption

dashboard tab. This issue occurs if users from different security domains share the same name.

For a scan event, duplicate values appear in the Data Asset Analytics repository.

You can use SalesForce as a data source in the SSIS scanner.

You can view the following attributes for the SAP BW/4HANA and SAP BW resources in Enterprise Data Catalog:

Query last execution time
ADSO last refresh time

You can configure the following resources to connect to the SAP server using a Secure Network Communications (SNC) connection:

SAP S/4HANA
SAP BW
SAP BW/4HANA

Users authenticated using SAML SSO can search for assets in Enterprise Data Catalog from an external portal.

The Amazon S3 resource includes the following enhancements:

You can extract metadata from an Amazon S3 compatible storage such as Scality RING.
You can use a temporary session token to connect and extract metadata from an Amazon S3 data source.

SQL statements for views and stored procedures are formatted to make them easier to read.

You can configure a Salesforce resource to use OAuth authentication to connect to a Salesforce data source.