Test Data Management All Products
After you reorder custom attributes and save the changes in the
Filter Settingstab, the order is not retained in the search results page.
You cannot view the lineage between the SAP HANA and Tableau Server resources because of the object ID difference.
You cannot identify the workspaces, datasets, reports, and dataflows that the Catalog does not process or skips during the Microsoft PowerBI resource metadata extraction.
The Microsoft PowerBI resource fetches the first 5000 workspaces, even if the PowerBI data source includes more workspaces.
If you match the table name in the SAP PowerDesigner data source with the table name in the Catalog, you cannot view the lineage between the database tables for an SAP PowerDesigner resource.
The Amazon S3 resource detects the file size of unstructured files as zero bytes.
Data Integration Service log file does not display profiling task details such as the profiling ID and timestamp in the messages.
Enterprise Data Catalog displays the value frequency of a column even if you do not have the Metadata and Data Read permission assigned to you.
You cannot view the non-sensitive data in the value frequency statistics of a column if you have the View Sensitive privilege.
If a resource name includes a hyphen (-) character, the composite data domain inference fails and the following error message appears in the log file:
com.infa.products.ldm.scanner.api.ScannerExecutionException: Inference operation is failed
When you run a profile on the JDBC resource, the catalog displays profile results of columns of timestamp data type and skips other data types.
You cannot assign data domains to assets of a custom resource.
Enterprise Data Catalog does not display the
Data Domainssection for assets of a custom resource.
If you run a profile on a Teradata resource using the JDBC profiling connection, Enterprise Data Catalog does not support the
LOCKING ROW FOR ACCESSfeature.
When you profile tables from an SQL server database, Enterprise Data Catalog skips columns of custom data types.
This issue occurs if you configure a resource using the ODBC profiling connection.