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

Community

Connector Improvement: Missing data using e-conomic connector

Answered
Adam Turcsany User

Hey,

We have started using the e-conomic managed connector to extract data from the source, however we have noticed that a lot of the data that is available through the API is not synced properly using the connector, mainly data related to account year,period etc.

The issue that we encountered is rooting from the fact that in some cases an accounting year is not like "2022" rather spanning over multiple years so "2022/2023", in that case the endpoints to extract further information for that accounting year looks different. Because of this we are losing more then 60% of the data available.

Steps to reproduce:
1. Send GET request to retrieve data for a given accounting year: For example for 2023 use: https://restapi.e-conomic.com/accounting-years/2023
2. Check response message: "Accounting Year '2023' not found!",

4. Send GET request to: https://restapi.e-conomic.com/accounting-years
5. Search for record where "year" is like "2022/2023".
6. Check eg. the "self" endpoint in the record: https://restapi.e-conomic.com/accounting-years/2022_6_2023

Can you please let me know if there is a chance that Fivetran can provide a fix for this or shall we look into creating a custom connector for this solution?

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Sisan Kumar Sahu Fivetranner

    Hi Adam,

    Thank you for your feature request regarding the Economic connector.

    If I understand correctly, your concern is that cases spanning across 2022 and 2023 may not be fully captured. If that’s the scenario you’re referring to, I’d like to clarify that we call the endpoints using the fromDate and toDate parameters. This approach should ensure that all relevant data within the specified range is retrieved, even when records span multiple years.

    Have you already created a support ticket so we can formally investigate this? If so, please feel free to share the ticket number.

    Additionally, you’re welcome to book time on my calendar so we can review this case together. I’d be happy to discuss it in more detail and better understand the specific behavior you’re observing.

    Best regards,
    Sisan