Connector Improvement: Bizzabo: Capture deletes for the registration table
Answered
In the Bizzabo system, some ticket registrations had their ticket types changed. This resulted in a new registration ID being created and the original registration ID being deleted in Bizzabo. However, these deletions were not captured by the Fivetran connector and the records continued to persist in Snowflake. We attempted a historical re-sync, but the deleted rows still remained.
We also saw that during the re-sync, the _fivetran_synced field was updated for all existing IDs, except for those rows that had been deleted in the source.
The only recommended action is to drop the table and reload it - potentially incurring FiveTran MAR charges. The reload time for this table is long and the table would need to be dropped and reloaded frequently to ensure continued accurate reporting.
Please can you update the Bizzabo connector to correctly capture deletes for the registration table?
-
Official comment
Hi Elspeth,
Thank you for reaching out and sharing your insightful feature request regarding the Bizzabo connector. We truly appreciate users like you who help us enhance our product with valuable feedback.
I'm pleased to inform you that your request to update the Bizzabo connector to correctly capture deletions for the registration table has been added to our backlog. Our team will prioritize this feature based on overall demand and impact.
Rest assured, we will keep you updated on any progress or developments regarding this feature. Please feel free to reach out if you have any further questions or additional feedback.
Best regards,
Syead Mujtaba Imam Rizwi
Please sign in to leave a comment.
Comments
1 comment