Release Notes > Metadata Command Center > Connector and connectivity issues

Connector and connectivity issues

Read the following pages to learn about fixed issues, known limitations, and third-party limitations that apply to connectors that you can use in your service. Consider the following guidelines for the release notes:

•If a connector has known or fixed issues, you will find it in the release notes even if the connector is not updated in the current release.
•If a connector does not have any notable known or fixed issues, you will not find it in the release notes.
•The (month, year) value in each issue description indicates the release in which the issue was fixed or reported.

Amazon Redshift V2 Connector

Fixed issues

The tables in this section describe recent fixed issues for Amazon Redshift V2 connector in Metadata Command Center. Not all monthly releases include fixed issues.

November 2025 fixed issues
July 2025 fixed issues

Issue	Description
SCAN-24111	When you specify additional parameters in the JDBC URL to connect to the Amazon Redshift cluster and run a catalog source job, Data Governance and Catalog appends the additional parameter to the database name.

Issue	Description
CDGC-79527	Data profiling tasks on databases fail with the following error: Workflow generation failed for object: java.lang.ClassCastException

Databricks Connector

Fixed issues

The tables in this section describe recent fixed issues for Databricks connector in Metadata Command Center. Not all monthly releases include fixed issues.

November 2025 fixed issues
July 2025 fixed issues
April 2025 fixed issues

Issue	Description
SCAN-25625	You can’t view the lineage for a View. This issue occurs if a Create View statement includes the ILIKE operator.
SCAN-26135	When you run a metadata extraction job, the job completes with the following warning: Unknown dataType
SCAN-27104	When you run metadata extraction jobs, the jobs fail with the following error: Unable to import Python custom module pyspark.sql.functions.cast" This occurs if the module is not included in the supported list of PySpark functions and is not available in the Databricks Python environment.

Issue	Description
SCAN-21280	When you run a catalog source job, the job succeeds with the following error in the debug logs: WARN Unknown dataType : timestamp WARN Unknown dataType : date
SCAN-19421	When you run a catalog source job, the job succeeds with the following error in the debug logs: Unknown column This issue occurs when the catalog source references a column within a temporary view and the temporary view contains the sum() and filter() aggregate functions.
SCAN-18675	When you run a catalog source job to extract a view created with a CREATE VIEW statement that uses a mount point, you can’t perform connection assignment. Data Governance and Catalog doesn't display the lineage or generate reference objects.

Issue	Description
SCAN-18686	When you run a job to extract lineage from a Unity Catalog source, the job succeeds with the following error in the debug logs: samples.accuweather.forecast_daily_calendar_metric
SCAN-17815	Metadata extraction jobs fail with a null point exception. This issue occurs when a notebook refers to another notebook with an incorrect relative path.
MDP-5953	When you run a data profiling job on tables from multiple databases, the job fails. This issue occurs when you do not specify the catalog source name in the connection properties.

February 2025 fixed issues

Issue	Description
SCAN-14903	When you extract metadata from a large number of views, the job fails with the following error: Out of Memory
SCAN-13823	When you run a catalog source job with the PySpark module and you use the net.snowflake.spark.snowflake.Utils.runQuery method, Data Governance and Catalog doesn't display the lineage and generates the following error: Unable to resolve sc._jvm.net

Google BigQuery V2 Connector

Fixed issues

The tables in this section describe recent fixed issues for Google BigQuery V2 connector in Metadata Command Center. Not all monthly releases include fixed issues.

July 2025 fixed issues

Issue	Description
SCAN-20256	When you run metadata extraction jobs on objects that include aggregate functions, the jobs fail with the following error: Failed to parse statement. Unable to parse script.
SCAN-20342	If a stored procedure contains a statement such as select (a, b) from c , the statement returns only one value instead of two. Since the value needs to be assigned to two variables, metadata extraction jobs fail with the following error: com.compactsolutionsllc.cdimc.common.visitor.tracking.TrackedException: Excessive SELECT INTO target at index 1. Number of available sources: 1

Greenplum Connector

Fixed issues

The tables in this section describe recent fixed issues for Greenplum connector in Metadata Command Center. Not all monthly releases include fixed issues.

July 2025 fixed issues

Issue	Description
SCAN-21080	Metadata extraction jobs fail to extract the Source Created By attribute value for partitioned tables.

Kafka Connector

Fixed issues

The tables in this section describe recent fixed issues for Kafka connector in Metadata Command Center. Not all monthly releases include fixed issues.

April 2025 fixed issues

Issue	Description
SCAN-17579	If a source system includes an invalid schema, metadata extraction jobs fail with the following error: Invalid default for field policy_id: null not a ["string","null"

Microsoft Azure Data Lake Storage Gen2 Connector

Fixed issues

The tables in this section describe recent fixed issues for Microsoft Azure Data Lake Storage Gen2 connector in Metadata Command Center. Not all monthly releases include fixed issues.

April 2025 fixed issues

Issue	Description
CDGC-74093	Profiling tasks don't work as expected if you add only an exclude filter for data profiling.

Microsoft Power BI Connector

Fixed issues

The tables in this section describe recent fixed issues for Microsoft Power BI connector in Metadata Command Center. Not all monthly releases include fixed issues.

November 2025 fixed issues

Issue	Description
SCAN-21204	When you run a metadata extraction job, the job completes with the following warning: Cannot resolve the DAX identifier due to unavailable reference This issue occurs if the job includes reports that access data set measures without a table qualification.

July 2025 fixed issues

Issue	Description
SCAN-20160	When you extract metadata from PowerQuery expressions, the job fails if an anonymous Power Query function includes an optional argument.
SCAN-20360	When you extract metadata from a Power BI report and the Data Analysis Expressions (DAX) that you use reference upstream table measures, the job fails with the following error: Cannot resolve the following DAX expression: <...> Reason: Cannot resolve the DAX identifier: <...>

April 2025 fixed issues

Issue	Description
SCAN-17264	If a paginated report contains IIF statements, metadata extraction jobs fail with the following error: WARN (ReportFieldAdderWithParserImpl:85) {/PowerBi_BIEVO/BI EVO - PCS/Paginated_Report_Dataset_Self_BI_Giornaliero_V39_Anagrafica_Rapporti (Report)/Paginated_Report_Dataset_Self_BI_Giornaliero_V39_Anagrafica_Rapporti#2 (Report)} - Could not parse expression:IIF
SCAN-17214	Metadata extraction jobs that include the Table.ToColumns, Table.ToRecords, Comparer.OrdinalIgnoreCase, List.Accumulate, or List.Buffer query functions fail with the following error: PowerQueryFailedProcessingHandler
SCAN-17158	When you edit metadata extraction filters of an existing catalog source with object references across multiple source systems, you can't save the changes and the process times out.
SCAN-15585	When you run metadata extraction jobs that include PowerQuery expressions, the jobs succeed with warnings.
SCAN-12828	When you perform connection assignment between Microsoft Power BI and SAP HANA Database catalog sources, the job succeeds, but the lineage shows calculation views as reference objects.

February 2025 fixed issues

Issue	Description
SCAN-15626	If you use the Date.ToText function in a query, metadata extraction jobs fail to parse the PowerQuery expression. This impacts the lineage information.
SCAN-15622	Metadata extraction jobs that include the MetricsDataConnector.GetMetricsDatapower query function fail with the following error: Could not resolve expression due to following exception. Will create emergency lineage using expected columns. Could not resolve external object with name: MetricsDataConnector.GetMetricsData .
SCAN-15614	Metadata extraction jobs don't complete if the source system contains tables with the same name in datasets that reference each other.

Microsoft SQL Server Connector

Fixed issues

The tables in this section describe recent fixed issues for Microsoft SQL Server connector in Metadata Command Center. Not all monthly releases include fixed issues.

July 2025 fixed issues

Issue	Description
SCAN-20787	When you run a Microsoft SQL Server catalog source job to extract metadata from objects that contain an UNPIVOT clause and an IN clause in which the pivoted columns are qualified, the job succeeds, but the lineage is incomplete.

PostgresSQL Connector

Fixed issues

The tables in this section describe recent fixed issues for PostgresSQL connector in Metadata Command Center. Not all monthly releases include fixed issues.

July 2025 fixed issues

Issue	Description
SCAN-21080	Metadata extraction jobs fail to extract the Source Created By attribute value for partitioned tables.

February 2025 fixed issues

Issue	Description
SCAN-15186	When you run a PostgreSQL job to extract metadata from functions, the job completes with the following message in the debug log: Failed to parse statement. Parse error (InputMismatch) on token: 'log'.

Salesforce Connector

Fixed issues

The tables in this section describe recent fixed issues for Salesforce connector in Metadata Command Center. Not all monthly releases include fixed issues.

November 2025 fixed issues

Issue	Description
SCAN-24211	When you run a catalog source job, the generated debug logs include sensitive information. This issue occurs if the catalog source job uses a connection configured with OAuth authentication.

SAP Datasphere Connector

Fixed Issues

The tables in this section describe recent fixed issues for SAP Datasphere connector in Metadata Command Center. Not all monthly releases include fixed issues.

November 2025 fixed issues

Issue	Description
SCAN-21071	When you run an SAP Datasphere catalog source job to extract metadata, the SAP Datasphere asset associations are not extracted.

SAP HANA Connector

Fixed issues

The tables in this section describe recent fixed issues for SAP HANA connector in Metadata Command Center. Not all monthly releases include fixed issues.

November 2025 fixed issues

Issue	Description
CDGC-86764	Data profiling tasks on SAP HANA Database tables fail with the following error: Invalid column name. This issue occurs if the tables contain columns with names that start with a slash (/).
MDP-10153	When you run a data profiling job with filters that include wildcards, the job ignores the filters and profiles all objects.
MDP-10563	Data profiling tasks on SAP HANA Database objects fail. This issue occurs if you apply a profiling filter on calculation views with names that contain a dot.
MDP-9818	When you run a data profiling job on a SAP HANA Database catalog source, the job fails with the following error: java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length 26 This issue occurs if you apply a profiling filter on calculation views that include wildcards.
SCAN-23369	When you run a metadata extraction job, the lineage is incomplete and does not include all assets present in the calculation view. The issue occurs because the extraction process does not read schema mapping information.

July 2025 fixed issues

Issue	Description
SCAN-20758	If calculation view names start with a forward slash (/) and don't include packages, metadata extraction jobs generate errors.

April 2025 fixed issues

Issue	Description
SCAN-17015	Metadata extraction jobs fail to parse RankView calculation views that don't include the ORDER BY clause.

SAP OData V4 Connector

Fixed issues

The tables in this section describe recent fixed issues for SAP OData V4 connector in Metadata Command Center. Not all monthly releases include fixed issues.

July 2025 fixed issues

Issue	Description
SCAN-23220	When you run metadata extraction jobs on SAP Datasphere catalog sources, the jobs fail with the following error: DS Execution issue Cannot invoke "com.google.gson.JsonObject.get(String)" because "srcAssetObj" is null

Snowflake Data Cloud Connector

Fixed issues

The tables in this section describe recent fixed issues for Snowflake Data Cloud connector in Metadata Command Center. Not all monthly releases include fixed issues.

November 2025 fixed issues
July 2025 fixed issues
April 2025 fixed issues
February 2025 fixed issues

Issue	Description
SCAN-24398	When you use an underscore in a metadata extraction filter, additional schemas that don’t match the filter get extracted. This issue occurs because in SQL the underscore (_) matches any single character.
SCAN-26566	If you configure metadata extraction filters to exclude stored procedures, tasks, pipes, and dynamic tables, you cannot view the row count value in the system attributes.
SCAN-27006	When you extract metadata from source systems that contain procedure parameter values that cannot be decoded, the metadata extraction jobs fail with the following error: Caused by: java.lang.IllegalArgumentException: Cannot parse parameter: A

Issue	Description
CDGC-78928	When you perform connection assignment to reference source systems, the job succeeds but the number of matched and unmatched objects doesn't match the number of extracted objects.

Issue	Description
SCAN-17398	Metadata extraction jobs don't parse the JavaScript function and the following error occurs: com.compactsolutionsllc.cdimc.common.visitor.tracking.TrackedException: Parse error (NoViableAlt) on token: '.' . Line.column: 9.4, Text: [ >.<Array.from]

Issue	Description
SCAN-13820	When you import a session from a Snowflake.Snowpark library into a stored procedure, the metadata extraction job doesn't extract statement assets. The following error appears in the scanner debug log file: ERROR (ScannerComponent - PythonImportStatementVisitor:58) {<fqn of the stored procedure>} - Unable to import Python custom module snowflake.snowpark.Session. The module will be treated as black-box: we'll keep the lineage in places when this module is used but we'll not provide and specific behavior of this module. If you have WHL file with this module source code then you can put in the scanners Python user modules directory and run the scanning again. If unsure you can raise an issue for the Scanners team to investigate if there are other options here.
SCAN-13841	If a stored procedure uses the snowflake.snowpark.Session.write_pandas()function to write pandas DataFrame to a table in the source system, the metadata extraction job does not extract statement assets.
SCAN-13840	If a stored procedure uses the DataFrame.to_snowpark_pandas() function to convert Snowpark pandas DataFrame or Series into Snowpark DataFrame, the metadata extraction job doesn't extract statement assets. The following error appears in the scanner debug log file: ERROR (ScannerComponent - PythonExpressionResolver:58) {<fqn of the procedure>} - Failed to resolve expression modin.pandas.to_snowpark()@21.32:21.63

Strategy Cloud Connector

Known issues

The tables in this section describe recent known issues for Strategy Cloud connector in Metadata Command Center. Not all monthly releases include known issues.

November 2025 known issues

Issue	Description
SCAN-28641	You can't extract metadata from reports.

Tableau V3 Connector

Fixed issues

The tables in this section describe recent fixed issues for Tableau V3 connector in Metadata Command Center. Not all monthly releases include fixed issues.

November 2025 fixed issues

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.

July 2025 fixed issues

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: - When you create a data source in the source system directly with database tables, the metadata extraction job generates the connection name in upper case. - When you create a data source with custom SQL queries or stored procedures in the source system, the metadata extraction job generates the connection name in the case that you provide.

February 2025 fixed issues

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.

Workday Mass Ingestion Connector

Known issues

The tables in this section describe recent known issues for Workday Mass Ingestion connector in Metadata Command Center. Not all monthly releases include known issues.

November 2025 known issues