Issue | Description |
|---|---|
SCAN-20234 | When you run a catalog source job that uses a parameter in a custom SQL query, the job fails with the following error: com.compactsolutionsllc.cdimc.app.modules.exceptions.InvalidInputException: There is no parser capable of parsing |
SCAN-20965 | When you run a catalog source job, the job fails with the following error: Cannot invoke 'com.compactsolutionsllc.cdimc.tableau.bi.module.model.input.DataSource.getId()' because 'dataSource' is null This issue occurs in Tableau reports that use parameter values for sheet styling and formatting when connected to a Google BigQuery datasource. |
SCAN-21123 | When you configure the filter to include metadata from a Tableau site name, metadata extraction jobs extract information for four site names instead of one. This issue occurs when a workbook is migrated between different sites, but the Tableau workbook still points to its old site. |
SCAN-21261 | When you run a catalog source job, the job assigns the same core.location property to assets with the same name. |
SCAN-21325 | When run a catalog source job on Tableau reports that contain empty rows and columns, the lineage tab doesn't display upstream lineage information for the Tableau report. |
SCAN-21564 | When you run a metadata extraction job to extract workbooks and you don't add filters, the job fails with the following error: Failed to download workbook <...> Reason: duplicate entry: <...> The issue occurs when you rename the original Default site to a new name and then create a new Default site. The system treats both the renamed site and the new Default site as Default, causing duplicate entries. |
SCAN-21623 | Catalog source jobs to extract metadata from workbooks that contain worksheets with empty column names in their filters don't extract the dashboards that contain these worksheets. |
SCAN-21977 | When you run a catalog source job on SAP HANA calculations under the _SYS_BIC schema, job fails with the following error: "_SYS_BIC is not assumed to contain multiple fields with name: Deal Size" This issue occurs because group names in the database are the same as the column names. |
SCAN-23293 | When you run a metadata extraction job on a workbook the job succeeds but includes incorrect data sources in the results. The issue occurs when multiple data sources have the same caption in a Tableau workbook. |
SCAN-24568 | When you run a metadata extraction job on a workbook, the job doesn't extract metadata from the workbook and completes with the following warning: Cannot invoke "java.lang.CharSequence.toString()" because "replacement" is null |
SCAN-25276 | When you run a catalog source job to extract metadata, the job skips workbooks that contain duplicate columns. |
Issue | Description |
|---|---|
SCAN-18918 | Metadata extraction jobs extract connection names with upper and lowercase. As a result, duplicate connection entries appear during connection assignment. This issue occurs in the following scenarios:
|
Issue | Description |
|---|---|
SCAN-14393 | Metadata extraction jobs fail to extract workbooks and the following error appears in the debug log files: Cannot invoke "String.replaceAll(String, String)" because the return value of "com.compactsolutionsllc.cdimc.model.Component.getName()" is null. This issue occurs if the Tableau workbook uses a published data source connection in the source system. |