Skip to main content

Community

Connector Improvement: Affinity Connector Urgent Improvement

Answered

Please sign in to leave a comment.

Comments

4 comments

  • Official comment

    Hi Lior Sulkin,

    Thank you for bringing this to our attention. I've added the Affinity Connector improvement request to our backlog, and we'll prioritize it based on customer demand. We understand the urgency and impact on your costs, and will keep you updated on any progress. Please feel free to reach out if you have any further questions or concerns.

    Best,
    Sanjeevv Maniram

    I am facing the same issue. Can you please look into this?

     

    whats the story here folks?  This is a big problem and part of the issue is that FiveTran is using the v1 of the affinity API.  A V2 of the API has been available for more than a year.  Can we get an update on when this available.  Her is a link to the documentation:  https://developer.affinity.co/#section/Introduction

    Similar issue here-- the current careless approach is creating three orders of magnitude of excess cost, time, and complexity for customers; there's no way for us to work with Fivetran in the long run if this isn't handled.