2022
The Sage Intacct connector is designed to allow you a user to move data into in, and out of, Sage Intacct on-demand financial application suite. As an Sage Intacct user, you can use DBSync's Sage Intacct connector to integrate any on-premise applications and legacy systems with Sage Intacct. This connector may also be used for integrating to integrate Sage Intacct with other on-demand or SaaS based applications - like CRM, E-Commerce, and others. Integrating with Sage Intacct consists of an XML request/response sent over an HTTPS connection. The technical details of this connection - such as request headers, error handling, HTTPS connection, etc. - are all abstracted elicited from the user to make implementation quick and easy.
Prerequisites
In order to establish a connection to your Sage Intacct account, from DBSync Sage Intacct connector, you'll need the following:
The Sage Intacct connector instance represents a single Sage Intacct account, including login credentials. If a user wishes to connect to multiple instances of the either sandbox/production then, s/he must create a separate connection for each and, configure the parameters accordingly. The table below table represent represents parameters required for opening the connection to Sage Intacct user instance.
Property | Description | Required |
---|---|---|
Company Id | company Id is the required field to login to Sage Intacct To locate the company ID in Sage Intacct, follow the steps below steps:
| yesYes |
User Id | user User ID to connect to Sage Intacct acccount. | yesYes |
Password | password Password of the Sage Intacct account. | yesYes |
Sender Id | Senderid Sender ID is your api gateway credentials. Contact support, or your account manager at Sage Intacct, for more details | yesYes |
Control password | Application Control / Sender Password is your API gateway credentials.Contact support, or your account manager at Sage Intacct, for more details. | yesYes |
DTD version | Sage Intacct API DTD Version. 2.1 and 3.0 DTD. | yesYes |
Host Url | Sage Intacct Gateway Url. we We default to 'api.Sage Intacct.com'. | yesYes |
After a connector is created within a project, set up the connector within the project. DBSync can then map to, and from, the systems which that are supported by our standard connector list and . It can then use Sage Intacct connector to retrieve data from, or send data to, Sage Intacct Platform.
click Click on the following link to know which link Connectors List to learn about all connectors we support Connectors Listsupport.
This section gives out Trigger properties of Sage Intacct connector that need needs to be set from Trigger section of DBSyncDBSync.
Property | Description | Required |
---|---|---|
QueryType | Get or GetList. | yesYes |
Batch size | Batch size of requests to process. | yesYes |
Query | 'selectSelect' query to get records from Sage Intacct. | yesYes |
The Sage Intacct Trigger allows dbsync DBSync core system to query entities from the Sage Intacct Backend services. Sage Intacct exposes a “get” and “get_list” interface which is masked using a “SELECT query syntax” exposed by the Sage Intacct connector. The “SELECT query” syntax is given below:
Code Block |
---|
select [ fld, fld2, fld3,…fldn / *] <fields> from <entity> where [<fld1> opr <fld2>] <single_condition> or/and[<fld1><opr> <fld2>,<fld3><opr><fld4>]|or/and[<fld5><opr><fld6] <multiple conditions> <where_clause> order_by <fld1> asc, <fld2> asc, <fld3> desc <order_by_clause> |
In the above-mentioned syntax:
Fields: The The fields are actually the attributes, or the elements, within an entity which that need to be fetched by the query. In case all the fields need to be fetched, an asterisk “*” could can be used.
Entity: The entity which needs to be fetched from the Sage Intacct Backend.
Where Clause: The “where” clause takes in a series of “or/and “ conditions which internally contain the logical expressions ( the operands) which need to be operated upon. Please note that only the first condition will have two expressions as operands and any other additional operand will be a single expression.
Please note that a “single_condition” is also supported which consists of a single expression in the where clause.
Order By Clause: The “order_by” clause allows the sort order to be specified for the fields fetched.
Note that, 'where', and, 'order_by', clauses are both optional and need not be specified. The “Query Type” property in Sage Intacct Trigger specifies specifies whether it is a list query or a single select query.
Following are some examples
Code Block |
---|
Select select * from customerCustomer selectSelect customeridCustomerid,nameName,parentidParentid,termnameTermname,custrepidCustrepid,shippingmethodShippingmethod,custtypeCusttype,taxidTaxid,creditlimitCreditlimit from customerCustomer selectSelect * from invoiceInvoice WHERE [whenmodified < 10/22/2010 00:00:00\] selectSelect recordnoRecordno,customeridCustomerid,nameName from customerCustomer whereWhere [customeridCustomerid = ZAB001] AND [recordnoRecordno = 24] selectSelect * from customerCustomer [key=Key_Value] |
This section gives out section lists Rule properties for Sage Intacct connector that need needs to be set during the Rule setup in DBSync.
Property | Description | Required |
---|---|---|
External id | External reference column to be used for upsertUpsert | required Required when 'write type' is 'upsertUpsert' |
Table | Name of table to write transaction | yesYes |
Max Batch Size | Batch size of requests to process | yesYes |
Write Type | Insert, Update or Delete. Limited support for upsertUpsert | yesYes |
Uses Of Sage Intacct Connector
The Sage Intacct connector makes it easy to work with Sage Intacct web service by:
Frequently Asked Questions
Q: How does DBSync connect to Sage Intacct?
A: DBSync connects to Sage Intacct platform through connector called Sage Intacct connector which . This has inbuilt API methods that open a connection to Sage Intacct application for reading, and writing, data in, and out of, the platform.
Q: Does DBSync need to be installed on the same machine as that of Sage Intacct?
A: The answer is No. Since both, As both of DBSync and Sage Intacct platforms, are available through the cloud and if cloud. If required DBSync is also available as on-premise version as well.
Q: How does Sage Intacct connector handle errors?
A: The DBSync Sage Intacct connector handles processing of errors in different ways depending on the error type and . Error can be tracked via log section of the DBSync platform. If there is a connection error, authentication error , or schema validation error then, process level error is triggered.