Connector Improvement: Upgrade Affinity connector from Lite to Standard
AnsweredThe current data schema is a bit too normalized - there are 34 tables for some fairly standard objects in Affinity. Because of this, there ends up being many tables that are essentially just rows of ids that serve as links to other tables. This creates many more rows than necessary - a less normalized build out would have less atomic data but aggregated better, meaning that certain objects in Affinity don't result in a high n number of rows for any given create, update, or delete. This not only makes the connector less complex to navigate the join structure but also cheaper given that fewer MAR are needed to achieve the same end result. Additionally, it would be great to select only certain objects to replicate data from Affinity. For example, I'm uninterested in the following objects: file, relationship_strength, and any of the interaction_chat objects. Unselecting these objects would not only reduce MAR and Fivetran costs for users but also reduce cloud storage costs too. Not everyone wants to bring over every single object.
-
Official comment
Hi Max Eagle,
Thank you for your detailed feedback on the Affinity connector. While upgrading the connector from Lite to Standard and adding more customization options is currently outside Fivetran's strategic focus, we are committed to enhancing our core value areas. We will continue to track interest in this feature and use it to inform future developments. Your insights are valuable to us, and we appreciate your understanding.
Best,
Sanjeevv Maniram -
can we get FiveTran to switch to the V2 of the Affinity API... https://developer.affinity.co/#section/Introduction
Please sign in to leave a comment.
Comments
2 comments