QuickBooks Online Connector v2.0 in ADF Failing for Tables with Underscores

Hello Mandar Zope!

Thanks for posting your Query on Microsoft QnA!

In addition to the apt and precise response of Vinodh247, Let’s address each of your questions with the most actionable guidance and current insights:

1. Are there any changes in how table names are parsed or resolved in the new version?

Yes, there are important differences, but official documentation does not suggest any changes related to underscore in the name. I am summarizing the changes for you.

• In version 2.0 of the QuickBooks Online connector, Microsoft now requires you to specify the tableName exactly in your dataset definition or to explicitly use the query property in the source definition.
• While underscores are permitted in QuickBooks object names, the handling of table names and possible quoting/escaping may differ from v1.0, and there is no published Microsoft documentation specifying a known parsing bug with underscores. However, community reports do suggest that how you reference (case, quotes, escaping) your table object is more strictly enforced in v2.0.

2. Is there a workaround to successfully extract data from these tables?

• Try the query Option: Instead of depending on the tableName parameter, define your source as a query. For many users, selecting the object via a native QuickBooks query (as supported by the API) bypasses the failure with underscored table names.
  • Example:

{
  "type": "QuickBooksOnlineSource",
  "query": "SELECT * FROM [Attachable_AttachableRef]"
}

Ensure you use the exact object name as defined by the QuickBooks API, including correct casing and underscores.

• Alternate Connectors: If the built-in connector continues to fail, consider third-party ODBC/OData connectors as a temporary measure. Some, like CData or Invantive, allow flexible referencing and may avoid this parsing issue entirely. Reference (https://www.cdata.com/kb/tech/qbonline-cloud-adf.rst)
• Check for Updates & Support Cases: Since there is no documented fix yet, it is highly recommended to log a Microsoft support ticket, referencing your scenario and observed behaviour. This will help escalate undocumented issues if present.

3. Are there additional diagnostic steps or logging options available?

• Enable ADF Activity Logging: You can turn on detailed diagnostic logging when running your ADF pipeline:
  • Set Enable Logging: true in your Copy activity.
    • Choose Logging Level: Info or Verbose for deeper insights.
      • Logs are typically sent to the configured Azure Storage Account. However, note that headers may be sparse for deeper connector-internal errors.
      • Log Analytics and Monitoring: You can route diagnostic logs to Azure Log Analytics for querying and visualization—which may help catch hidden connector or HTTP request issues.

References

• For official details and updates:
  • Copy data from QuickBooks Online (ADF documentation)
  • Sample community thread on this issue
  • Logging and diagnostics guidance

There’s no official bug with underscores documented, but v2.0 is stricter on table name resolution and quoting. Use the query property as a workaround, enable detailed logging, and consider opening a Microsoft support case if needed.

Please do "Accept as Answer" or Upvote if the response provided is useful, so that you can help others in the community looking for remediation for similar issues.

Hello Mandar Zope!

Hope you are having a good day!

Just curious if you have gone through my response for your issue? If it worked then could you please do an "Upvote" or "Accept an Answer" so that it would help other community members.

Thanks

Pratyush

Hi

Thank you for the detailed insights and suggestions.

I have attempted the approach using the query-based source definition as recommended:

{ "type": "QuickBooksSource", "query": "SELECT * FROM Attachable_AttachableRef" }

However, I am still encountering the same error:

Failure happened on 'Source' side. Type=Microsoft.DI.Connector.QuickBooks.Exceptions.QuickBooksConnectorException, Message=Exception has been thrown by the target of an invocation., ErrorCode: InternalError, Source=Microsoft.DI.Connector.QuickBooks

Please advise if there are any additional configuration steps, known limitations, or patches that can help resolve this issue.

Hello Mandar Zope ,

Thanks for sharing your insights. Unfortunately, I can't replicate the issue at my end since Quickbooks are not available in India not even for the trials.

I will be taking your issue further to the next level. You will be notified for any further findings.

Thanks

Pratyush