Connector Improvement: Improved Options on freshdesk connector for time_entries
AnsweredHello,
We're currently using the freshdesk connector with the time_entries table enabled. We're aware that since the Freshdesk API doesn't enable delete checks, you have to fully re-sync all time_entries once a month to check for deleted entries.
This is an issue for two reasons:
- We're charged for every record updated when this sync occurs. It accounts for 90% of our MAR on the connector, and is costing us a lot.
- This sync takes a while. Recently it timed out, causing a two week outage of the time_entries sync.
As our data grows, the problem is bound to get worse. We'd love to see some improvements, or increased optionality on this connector. Some ideas:
- Only checking for deleted time_entries on tickets created in the past 90 days
- Only checking deletes on time_entries that were created in the past 90 days
- Giving us a refund on the MAR charged for re-syncing old time_entries
Let us know if any of this is possible!
Thanks,
Geoff
-
Official comment
Hi Geoff,
Thanks for writing in with this feedback. We are aware that this behavior is not ideal and always looking for ways to improve it. One feature that we have planned is to allow you to choose a historical sync time frame for your Freshdesk connector. Currently, we sync all historical data available, but this option would allow you to choose to have Fivetran only since the last 1 year of data, or 2 years, etc. This would also mean that on resyncs (e.g. time_entries), data would only be resynced from the date you've chosen in connector setup. This would help solve the problem of time_series taking a long time to resync monthly, but it would also apply across the board to other tables as well.
I'd be happy to hear your feedback on this - would it be a feature you're interested in?
Best,
Sadie
Please sign in to leave a comment.
Comments
1 comment