Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Complete version data for tables subscription and subscription_order_charge

Answered
Jakob Gille User

Hey! My request concerns the tables subscription and subscription_order_charge for the "Younium" connector. Both tables contain only the latest version of the objects that they list. This causes problems when attempting to join these tables to other tables. The reaseon is that each new version of a subscription or subscription order charge has a new ID. The ID is the primary key of the table. So since not all versions are included in the table, this means that there are lots of primary keys missing. Therefore, other tables using these IDs as foreign keys can't be joined properly to the tables subscription and subscription_order_charge.

Personally, I would not mind getting all the historic versions into the existing tables. But for other users of these tables, that may become confusing. So an option could be to create two new tables called subscriptions_all_versions and subscription_order_charge_all_versions. Or something similar. I suspect this would require less communication to roll out. 

Please let me know if anything needs further explaining or if I can help in some other way. I am happy to jump on a call if needed too. 

Kind regards, Jakob G

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Sanjeevv Maniram T Fivetranner

    Hi Jakob,

    Thank you so much for taking the time to share your detailed feature request regarding the Younium connector. We truly appreciate feedback from users like you, as it helps us understand the needs and challenges faced in various use cases.

    At this moment, adding all historical versions to the subscription and subscription_order_charge tables isn't on our current roadmap. However, your suggestion to potentially create new tables for all versions is certainly intriguing and could be a valuable enhancement for many users.

    To help us gauge the broader demand for this feature, I encourage other users who find this valuable to upvote it on our feature request portal. The more interest we see, the better we can prioritize it for future development cycles.

    Please know that while this isn’t prioritized right now, we’re always open to revisiting requests as user needs evolve. Your willingness to engage further on this matter, including offering to clarify or discuss more deeply, is greatly appreciated.

    Thank you once again for your input and understanding.

    Best,  
    Sanjeevv Maniram T