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

Community

Connector Improvement: Sage Intacct - Custom Fields Support

Cason Male User

Hello,

We've been using the Sage Intacct connector for some time now and it's been very beneficial to our business. Currently it seems fivetran does not support syncing custom fields from Sage Intacct.

We are migrating a legacy ERP system (Netsuite) into our main one (Intacct) and there are a handful of custom fields we created in Intacct to handle some of the data coming from Netsuite. These are primarily custom SO transaction definitions that the old system required, i.e. special Sales Order, asset orders and shipping order types. 

Best,

Cason

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Official comment
    Sandeep Preetam Saila Fivetranner

    Hi Cason

    We are happy to announce that we are currently supporting custom fields in SO_DOCUMENT, and SO_DOCUMENT_ENTRY objects. Please let us know in case you want them supported in other endpoints.

    Best
    Sandeep
    Technical Product Owner

  • Cason Male User

    Hi Sandeep,

    That's great news. However we're not seeing the custom fields come through yet in fivetran such as COMPOLOGY_SALES_ORDER. It looks like the sync is really slow and partially interrupted as well. Is this due to pulling all historical custom fields? We were seeing this type of syncing behavior previously when fivetran switched us to the new Intacct query method, replacing the legacy readByQuery method. We asked to be switched back to the legacy method due to syncing performance issues. 
     
    As for other objects, could you also include custom fields to the following objects:
    INVDOCUMENT and INVDOCUMENTENTRY
     
    Thank you,
    Cason
  • Sandeep Preetam Saila Fivetranner

    Hi Cason,

    We are sorry to hear that you've been facing sync issues with Sage Intacct.

    We have recently implemented several performance improvements to Sage Intacct. One of these enhancements includes utilizing Query instead of the legacy ReadByQuery to fetch data, which offers several advantages. While we have ensured that using Query does not impact sync performance, if you continue to experience issues, I recommend raising a support ticket so our team can investigate the case in detail.

    Additionally, I have added your feature request to our backlog. We will prioritize it based on demand and keep you updated on any developments.

    Best,
    Sandeep

  • Cason Male User

    Hi Sandeep, 

    I have an active ticket regarding the degraded sync performance using the new Query method over the legacy ReadByQuery method. We have already proven from a previous ticket that the degraded performance is due to the new sync method so I will ask them again to revert it. 

    As for the custom fields in SO_DOCUMENT, and SO_DOCUMENT_ENTRY objects, I am still not seeing them in the schema. Could you provide an example of custom fields and confirm they are available?

    Thanks,

    Cason

  • Sandeep Preetam Saila Fivetranner
    • Edited

    Hi Cason

    I see that support has already initiated a conversation with the tech team for this case. I will also follow up on it and see that we resolve the issues ASAP.

    Best
    Sandeep