Productboard connector limitations

Important

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

The managed Productboard connector in Lakeflow Connect syncs only the notes table incrementally, captures deletes only for archived notes, and ingests complete relationship data only for features and components.

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 Productboard connector.

• Only the notes table syncs incrementally. The connector reingests all other tables in full on every sync.
• The connector handles deletes only for the notes table, through the archived field. It doesn't detect notes that are permanently deleted in Productboard.
• The inline relationships column on entity tables holds only the first page of each record's relationships. The complete set is available only for features and components, in the feature_relationships and component_relationships tables.
• The connector doesn't ingest complete relationship data for products, companies, users, release groups, releases, objectives, key results, initiatives, or notes.
• The connector doesn't ingest Jira or plugin integration configuration data.
• The connector doesn't have a separate tags table. Feature tags are in the fields column of features, and tag definitions are in field_definitions.