Skip to main content
Last updated on

QuickBooks connector limitations

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for QuickBooks from the Previews page. See Manage Databricks previews.

This page contains information about known limitations of the managed QuickBooks connector in Lakeflow Connect.

General software as a service (SaaS) connector limitations​

The limitations in this section apply to all SaaS connectors in Lakeflow Connect.

  • When you run a scheduled pipeline, alerts don't trigger immediately. Instead, they trigger when the next update runs.
  • When a source table is deleted, the destination table is not automatically deleted. You must delete the destination table manually. This behavior is not consistent with Spark Declarative Pipelines on Lakeflow behavior.
  • During source maintenance periods, Databricks might not be able to access your data.
  • If a source table name conflicts with an existing destination table name, the pipeline update fails.
  • Multi-destination pipeline support is API-only.
  • You can optionally rename a table that you ingest. If you rename a table in your pipeline, it becomes an API-only pipeline, and you can no longer edit the pipeline in the UI.
  • If you select a column after a pipeline has already started, the connector does not automatically backfill data for the new column. To ingest historical data, manually run a full refresh on the table.
  • Databricks can't ingest two or more tables with the same name in the same pipeline, even if they come from different source schemas.
  • The source system assumes that the cursor columns are monotonically increasing.
  • The connector ingests raw data without transformations. Use downstream Spark Declarative Pipelines on Lakeflow pipelines for transformations.

Connector-specific limitations​

The limitations in this section apply to the QuickBooks connector.

Full refresh schedule​

  • The connector uses the QuickBooks Change Data Capture (CDC) endpoint to fetch incremental changes. This endpoint returns changes from only the last 30 days, so schedule the pipeline to run frequently. If the pipeline doesn't run for more than 30 days, run a full refresh to ingest changes that the endpoint no longer returns.

Deleted records​

  • Deletes for the time_activity and tax_agency tables are applied only when you run a full refresh.
  • In the account, class, customer, customer_type, department, employee, item, payment_method, term, vendor, company_currency, and tax_rate tables, records that are made inactive in QuickBooks are deleted from the destination table.

Incremental ingestion​

  • The tax_code, company_info, preferences, and tax_classification tables don't support incremental ingestion. Each pipeline run reingests all records for these tables.

QuickBooks-imposed limitations​

  • QuickBooks supports at most three custom fields on transactions, and only on the invoice, estimate, credit_memo, sales_receipt, refund_receipt, and purchase_order tables.
  • After you turn on multicurrency in QuickBooks, you can't turn it off.
On this page