Chargebee subscription_entitlement table delete captures.
AnsweredWhich connector?:Chargebee
Additional details: the source does not provide a field or mechanism to identify deleted records in the subscription_entitlement table. Therefore, a resync is currently required to capture deleted records. I'd like to request native delete capture support as having to re-sync table to get accurate data might not be the sustainable solution when tables are getting bigger
-
Official comment
Hi Roman,
Thank you for the request.
We have added delete capture for the subscription_entitlement table to our active backlog. Chargebee does not expose a delete flag for this table, so we are reviewing what is possible. How large is the table today, and how often do you resync it? We will keep you updated on this thread.
Best,
Syead Mujtaba Imam Rizwi -
Hi Syead!
Currently the table is around 250K rows. I'm intended to re-sync table once a day to reconcile, although we should have near-real time data for our needs for operational dashboard.
Maybe it is possible to pull events with deletions and delete it like that?
thanks!
Please sign in to leave a comment.
Comments
2 comments