When you use a Microsoft Power BI MetaDex scanner to extract metadata, you might see a 50 percent increase in the asset count.

When you use an IBM DB2 resource to extract the stored procedures, the IBM DB2 resource skips the matched functions.

When you use a Teradata resource to the extract stored procedures, the Teradata resource skips the matched functions.

If you search and select attributes during export, the exported Excel contains the last attribute selected instead of the Data Owner.

If you run a resource from pre upgrade into the post upgraded environment, the Cloudera Navigator scanner shuts down unexpectedly.

Databricks Advanced Scanner Type option incorrectly appears twice under the Resources tab.

Fields tab for Amazon S3 Asset Type JSON fails to show the hyperlink for the data domain.

If you follow a table, add a Busiiness term, and choose to add or remove a user from People panel, the notifications shows the details of the user along with the Business term.

While refreshing the 360 Overview resource page, incorrect notifications appear for the Follow or Unfollow option.

Microsoft Azure SQL profiling fails with the invalid column name '*'" error.

The Display Name enrichment for the Business Title fails to get imported at the resource level using the Enrichment Migration Utility.

When you restore enrichments using import or export with CSV in the LDM Catalog, the Custom Attributes gets duplicated.

The Dataset Profile Filter option in Discovery incorrectly shows regex as a schema option in the UI.

Glue online scanner with reference object enabled for the database filter

perfdb, perfdb_set2, perfdb_set3

fails.

Composite data domains are not shown in the Overview and Columns tab.

The Discovery tab on the Enterprise Data Catalog UI fails to show the columns names even if it is present in the xdocs.

After you run the V2 scanner with the Enrichment Migration Utility, the data domains are incorrectly present in both the original and curated state in the V2 scanner.

After you run the enrichment migration utility, the data domain enrichment source links incorrectly appear twice in the object API response.

The enrichment migration utility cannot migrate the Business Glossary terms, Data Domain associations, and Rejected or Accepted Business and Axon terms.

Date picker fails to open for the custom attribute of multiple date type.

After you run the enrichment migration utility, the business title incorrectly moves from the Accepted state on the V1 scanner to the Recommended state on the V2 scanner.

The system attribute for the Axon term shows the <p> and </p> tags in the UI.

Failed to use the custom catalog URL for the digest notification emails.

After you run the Enrichment Migration Utility, you can see the default facts, such ascore.classType's providerId gets changed and causes Catalog data corruption.

When extract metadata with a Microstrategy scanner, you might see an increase in the asset count.