Data Ingestion and Replication Release Notes > Application Ingestion and Replication > 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:

NetSuite Mass Ingestion Connector

Known issues

The following table describes known issues:
Issue
Description
AIN-7897
When you resynchronize a NetSuite source with the Resync (refresh) option in an application ingestion and replication combined load job, schema drift changes are not applied, and the target tables are not re-created with the latest DDL changes. (April 2025)

SAP OData V2 Connector

Known issues

The following table describes known issues:
Issue
Description
AIN-7994
When you use SAP OData V2 as a source in an application ingestion and replication task, where the SAP OData V2 connection includes a '/' at the end of the service URL for the default service type, the task is unable to retrieve the schemas from the source.
Workaround: Ensure that no trailing '/' occurs at the end of the following service URL: http://<Host name of the SAP server>:<Port number>/sap/opu/odata/sap/<Service name>
(April 2025)
AIN-7885
An application ingestion and replication task that extracts data that has the D16R or D38R data type from an SAP OData source and loads it to an Azure Synapse Analytics target fails with a metadata handler error. (April 2025)
AIN-7883
An application ingestion and replication task that extracts data that has the Boolean data type from an SAP OData source and loads it to a Google BigQuery target fails with a metadata handler error. (April 2025)