Establishing a Connection
Authenticating to Sage Intacct
To authenticate, set CompanyID and set User and Password to the credentials you use to log on to Sage Intacct.
Connecting to Sage Intacct
To connect to Web Services, you will first need to enable the Web Services subcription. Navigate to Company > Admin Tab > Subscriptions and enable Web Services. Intacct also reccomends creating a Web Services-only user, which can be done by navigating to Company > Admin Tab, and clicking on the + sign beside Web Services users.
Our Intacct driver has embedded Web Services credentials that will be used when reading data from Intacct. To use the embedded credentials, do not specify anything for SenderID and SenderPassword. Then, in your Web Services dashboard, navigate to Company > Company Info > Security tab and add CData to your Web Services authorizations.
To use your own Web Services credentials to write data to Intacct, set the SenderID property to the Web Services Sender ID assigned to you by Sage Intacct and set the SenderPassword property to your registered Web Services password, in addition to the authentication values above.
To connect to a shared child company, additionally set LocationsID. To connect to a distributed child company, set ClientID instead.
Connecting Through a Firewall or Proxy
To connect through the Windows system proxy, you do not need to set any additional connection properties. To connect to other proxies, set ProxyAutoDetect to false.
In addition, to authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.
Set the following properties:
- To use a proxy-based firewall, set FirewallType, FirewallServer, and FirewallPort.
- To tunnel the connection, set FirewallType to TUNNEL.
- To authenticate, specify FirewallUser and FirewallPassword.
- To authenticate to a SOCKS proxy, additionally set FirewallType to SOCKS5.
Troubleshooting the Connection
To show provider activity from query execution to network traffic, use Logfile and Verbosity. The examples of common connection errors below show how to use these properties to get more context. Contact the support team for help tracing the source of an error or circumventing a performance issue.
- Authentication errors: Typically, recording a Logfile at Verbosity 4 is necessary to get full details on an authentication error.
- Queries time out: A server that takes too long to respond will exceed the provider's client-side timeout. Often, setting the Timeout property to a higher value will avoid a connection error. Another option is to disable the timeout by setting the property to 0. Setting Verbosity to 2 will show where the time is being spent.