Transformations: Handle stripe update api better
AnsweredEx: when a subscription schedule is updated with a new "phases" object, fivetran just adds the phases and phase_plan into the tables without marking the previous phases and phase_plans as _fivetran_active=false or replacing them. There is no way to tell a subscription schedule update has occured because there is no historical context. I understand that historical data is not supported with every table for stripe, but if that can't be done, the second best thing to do is to replace the previous data with the updated data. The current implementation is not viable for accurately querying on the correct metrics and there is no way to track historical data with subscription schedule updates, which is a big issue.
-
Official comment
Hi Moshe,
We hope this message finds you well. We are currently reviewing older feature requests as part of our roadmap planning and wanted to check if you are still interested in the "Transformations: Handle stripe update API better" feature. Your input is invaluable in helping us determine the continued relevance of this request or if your requirements have evolved.
Thank you for your feedback and support.
Best,
Sandeep
Please sign in to leave a comment.
Comments
1 comment