Connector Improvement: Sage Intacct: Detect Deletes on Custom Objects
AnsweredCurrently, the Sage Intacct connector can't detect when we delete a custom object. These objects load with a `_fivetran_deleted` field that is always false, which is misleading. Per the Fivetran docs, this is a limitation on the Intacct API itself.
Our request: work with Sage to have them add the functionality Fivetran requires to track these deletes, then implement delete detection on custom Intacct objects on the connector.
-
Official comment
Hi Daniel,
We are definitely interested in working with Sage to provide this functionality for our customers. While the chances of direct collaboration with Sage are low, we’d love for any of our customers to help facilitate this collaboration.
I’d be happy to discuss this further—let me know if you'd like me to send you an email!
Best,
Sandeep -
Hi Daniel,
We wanted to follow up on the investigation into delete detection for Sage Intacct custom objects. Our engineering team has confirmed that the Sage Intacct AUDIT HISTORY API does not return events for custom objects, which means there is currently no API-level mechanism for Fivetran to detect deletes on those objects. Until Sage adds support for custom object events in their API, this feature isn't feasible on our end.
We'll keep this request open and revisit if Sage updates their API. If you have a direct relationship with Sage support, raising this with them would be the most effective path to getting this capability added.
Best,
Sandeep
Please sign in to leave a comment.
Comments
2 comments