Zoho CRM connector limitations

Important

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

This page contains information about known limitations of the managed Zoho CRM 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 Zoho CRM connector.

Deleted records

• The connector doesn't propagate deletes. Records deleted in Zoho CRM remain in destination tables until you run a full refresh.
• Removing a line item from a quote, sales order, purchase order, or invoice doesn't remove the row from the item table until you run a full refresh.

Tables and fields

• The connector doesn't make available subform and linking-module child tables, event participants, or an activities table. To ingest activities, use the tasks, calls, and events tables.

Incremental ingestion

• The roles, profiles, currencies, organization, contact_roles, territories, stages, and user_territories tables don't support incremental ingestion. Each pipeline run reingests all records for these tables.
• Changing a formula field's definition can change its values without updating the record's Modified_Time. Run a full refresh after you change a formula definition.

Feature-gated tables

• The territories and user_territories tables require Territory Management, which is available in Enterprise edition or above. When Territory Management isn't enabled, these tables fail. See Territory Management not enabled.
• The currencies table requires Multi-Currency, which is available in Professional edition or above.