EXEC SUMMARY
I’m pulling in data from HubSpot using the Azure Data Factor HubSpot connector. Generally works fine but for two of the available entities, I get the error below when previewing or pulling data; I’ve isolated the fields provoking the error and my workaround is to skip them but I’d rather not.
Two questions:
(a) any insights on the problem?
(b) working with HubSpot support I was directed to this forum but also a firm called ZappySys. Their site doesn’t seem to mention the ADF HubSpot connector as one of their products, only SSIS connectivity. Anybody have insights into that?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DETAILS
The tables where I get the error:
contacts_properties_options
deal_properties_options
Here’s when I get the error:
(1) when I try to preview data within Azure Data Factory, I get this (only for the two tables, others work fine):
ERROR [HY000] [Microsoft][Hubspot] (120) Error converting 0.0 to type boolean.
Activity ID: 6a89d90d-0d06-4c34-80f0-bc76614b23da
(2) when I create a pipeline with a Copy activity and set it to auto-create a table on the SQL-Server side, I get this error (but only for the two tables, others work fine):
Failure happened on ‘Source’ side. ErrorCode=UserErrorOdbcOperationFailed,‘Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ERROR [HY000] [Microsoft][Hubspot] (120) Error converting 0.0 to type boolean.,Source=Microsoft.DataTransfer.ClientLibrary.Odbc.OdbcConnector,’‘Type=System.Data.Odbc.OdbcException,Message=ERROR [HY000] [Microsoft][Hubspot] (120) Error converting 0.0 to type boolean.,Source=HubspotODBC_sb64.dll,’
(3) I did some exploration and noticed that these are the columns auto-created on the SQL-Server target side for the two tables:
[Options_Index]
[Options_Description]
[Options_Value]
[Options_Label]
[Options_Display_Order]
*[Options_Hidden]
*[Options_Read_Only]
*[Options_Double_Data]
The three marked with a star are bit datatype in SQL.
When I set up my Copy process in the pipeline with an explicit SELECT statement, and include all columns -- same error. But when I remove the last three columns, the error goes away. So evidently those are the ones affected by the problem on the source side.