Test Data Management 10.5
- Test Data Management 10.5
- All Products
On the execution of Power BI, the Advanced Scanners processing log does not show an error for when you specify a workspace that does not exist.
For the Greenplum database, Advanced Scanners fails to parse arrays. The following error message is displayed:
Advanced Scanners cannot read JSON, XML, and PDF file types from PowerBI Cloud. The Advanced Sanners log returns the following error:
For the Greenplum database, Advanced Scanners is unable to read a function when called from another function. You cannot analyze nested function calls.
When you run a PowerBI scan, Advanced Scanners extracts all connections in lowercase, instead of the original case from all file paths.
Advanced Scanners repository does not show lineage in Oracle ODI visualizations.
Advanced Scanners does not show the required attributes for Microsoft Power BI objects.
In Advanced Scanners
Linage and Impacttab, you cannot expand a Windows PowerBI Dashboard asset.
In Advanced Scanners, for Microsoft PowerBI, when you use the "Exclude:Workspace:Report" filter, the entire workspace is excluded.
Advanced Scanners does not list versions of generation data groups (GDGs) in the lineage. For example, when you call a file in JCL, use just the file name and not its previous version number (+1).
Advanced Scanners displays improper lineage for Windows PowerBI configuration execution with Web DataSet.
In Advanced Scanners, when you run a Talend configuration, a Calculation icon is displayed for configurations with column values created with the expression logic.
In Advanced Scanners, the memory footprint is very high when you run the Oracle scanner with 5000 stored procedures.
infacmd ldm restoreContentscommand fails with the following error:
[[BackupRestoreClient_20016] The ZIP file /data1/Informatica/LDM1050/Backup.zip used to restore data is not a backup store's data backup ZIP file.].
Workaround: Perform the following steps:
When the Informatica domain is enabled for SSL, the client certificates are not generated correctly when you enable the Catalog Service if passwordless SSH connection is not configured between the Catalog Service node and the Informatica Cluster Service gateway host.
Workaround: Configure passwordless SSH connections between the Catalog Service node and the Informatica Cluster Service gateway host.
When you access the Catalog Administrator using a browser configured with a non-English language setting, the following walkthroughs do not launch:
If you set the
-DcustomScannerMaxFileSizeJVM option value higher than the default value, the custom metadata and custom lineage resources fail.
You cannot open assets of offline resources in Enterprise Data Catalog.
SAP S4/HANA full scan fails with the OutOfMemory exception for Medium memory configuration setting.
For HDI SPARK cluster, when you select WASB as the storage type, HDFS Scanner test connection fails.
For Microsoft Power BI, Advanced scanners does not support the connection to ADLS Gen2.
For Microsoft Power BI, Advanced Scanners does not support a connection to ODBC Oracle.
You cannot accept or reject data domains of a custom resource.
When you navigate to the compact lineage view from the classic view, the Lineage and Impact tab fails to load after you click a table name in the view.
When you apply or rollback 10.5.0.1 from version 10.5, the 10.5.0.1 installer log file displays the following error message:
Microsoft Power BI execution fails if the report connects to Teradata.
For Microsoft Power BI, if you use a data set that has a Merged Query operation in PowerQuery, you cannot view lineage to the source. The logs contain the following warning:
Unable to evaluate PowerQuery expression. Unknown object: QueryName Call stack: Merged Queries, QueryName
For Microsoft Power BI, you cannot see columns extracted for the report in the Enterprise Data Catalog.
For Microsoft Power BI configuration, Advanced Scanners does not display the lineage if you import the data set from the web.
In a Microsoft Power BI Cloud Reader configuration, when you select files in
Reader mode, execution fails.
Microsoft PowerBI queries that include data set created from Azure Blob are not fully extracted. Extraction ends on the directory structure.
For Snowflake External Stage (S3), the lineage has a redundant loop between stage and S3.
Greenplum scanner fails when processing an INOUT parameter.
Greenplum scanner fails when processing a CURSOR statement.
Greenplum scanner fails when processing a SELECT INTO statement.
For the relational resource, on the
Columnstab, some columns do not appear on the list after migration.