Sage Intacct ADO.NET Provider
SQL-based Access to Sage Intacct through ADO.NET for your custom .NET applications and SSAS.
download buy nowOther Sage Accounting Technologies
Other Sage Accounting Drivers
-
-
Sage 300
learn more » -
Sage Business Cloud Accounting
learn more » -
Sage 50 UK
learn more »
The Sage Intacct ADO.NET Data Provider enables user to easily connect to Sage Intacct data from .NET applications. Complete read-write access to Sage Intacct enables developers to search (Contacts, Invoices, Transactions, Vendors, etc.), update items, edit customers, and more, from any .NET application.
Sage Intacct
Sage Intacct .NET Connectivity Features
- Powerful metadata querying enables SQL-like access to non-database sources
- Push down query optimization pushes SQL operations down to the server whenever possible, increasing performance
- Client-side query execution engine, supports SQL-92 operations that are not available server-side
- Connect to live Sage Intacct data, for real-time data access with the Sage Intacct ADO.NET Provider
- Full support for data aggregation and complex JOINs in SQL queries
- Secure connectivity through modern cryptography, including TLS 1.2, SHA-256, ECC, etc.
- Seamless integration with leading BI, reporting, and ETL tools and with custom applications via the Sage Intacct Connector.
Target Service, API
The CData JDBC Driver for Sage Intacct connects with the Sage Intacct Web Services API.
Schema, Data Model
The CData JDBC Driver for Sage Intacct models Sage Intacct data as an easy-to-use SQL database.
The data model of the driver is dynamic. This means that, when you connect using the driver, any changes you make in the Sage Intacct UI, such as adding a new table, adding new columns, or changing a column's data type, are automatically included in the schema of the driver.
Key Objects
The driver supports regular GL, Journals and more as Tables that you can read and write. The driver also supports various views such as Account Balanace, AP / AR, Purchase Order etc.
Operations
SELECT, INSERT, UPDATE, DELETE are supported. You can JOIN, Filter, GROUP BY and perform other basic clauses.
Authentication
Sage Intacct supports two types of authentication: Basic and Okta.You can establish a connection to Sage Intacct using embedded credentials (Basic authentication) or your own Web Services credentials, or Okta credentials.
See what you can do with Sage Intacct ADO.NET provider
Use Sage Intacct from SQL Server Analysis Service (SSAS) multi-dimensional cubes. Keep your analytical data modeling and access to any source including cloud and on-premises.
The Sage Intacct ADO.NET Provider allows developers to build applications that connect to Sage Intacct using familiar SQL and Entity Framework. Integrate Sage Intacct to your mission -critical applications or create easy side-by-side applications.
You can connect from ADO.NET compliant low-code development tools:
You can connect Sage Intacct from .NET-based reporting and analytics tools:
Standard ADO.NET Access to SageIntacct
The Sage Intacct ADO.NET Provider offers the most natural way to access Sage Intacct data from any .NET application. Simply use Sage Intacct Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Sage Intacct Data Provider through Visual Studio Server Explorer, in code through familiar classes, and in data controls like DataGridView, GridView, DataSet, etc.
The CData ADO.NET Provider for Sage Intacct hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
Working with DataAdapters, DataSets, DataTables, etc.
The Sage Intacct Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: SageIntacctConnection, SageIntacctCommand, SageIntacctDataAdapter, SageIntacctDataReader, SageIntacctDataSource, SageIntacctParameter, etc. Because of this you can now access Sage Intacct data in an easy, familiar way.
For example:
using (SageIntacctConnection conn = new SageIntacctConnection("...")) {
string select = "SELECT * FROM Contacts";
SageIntacctCommand cmd = new SageIntacctCommand(select, conn);
SageIntacctDataAdapter adapter = new SageIntacctDataAdapter(cmd);
using (adapter) {
DataTable table = new DataTable();
adapter.Fill(table);
...
}
}
More Than Read-Only: Full Update/CRUD Support
Sage Intacct Data Provider goes beyond read-only functionality to deliver full support for Create, Read, Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the Sage Intacct Data Provider as easily as interacting with a database table.
using (SageIntacctConnection connection = new SageIntacctConnection(connectionString)) {
SageIntacctDataAdapter dataAdapter = new SageIntacctDataAdapter(
"SELECT Id, Where FROM Contacts", connection);
dataAdapter.UpdateCommand = new SageIntacctCommand(
"UPDATE Contacts SET Where = @Where " +
"WHERE Id = @ID", connection);
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");
DataTable ContactsTable = new DataTable();
dataAdapter.Fill(ContactsTable);
DataRow firstrow = ContactsTable.Rows[0];
firstrow["Where"] = "New Location";
dataAdapter.Update(ContactsTable);
}
ADO.NET Provider Performance
With traditional approaches to remote access, performance bottlenecks can spell disaster for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential to create these problems. Common issues include:
- Network Connections - Slow network connections and latency issues are common in mobile applications.
- Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
- Large Data - Intentional or unintentional requests for large amounts of data.
- Disconnects - Complete loss of network connectivity.
The CData ADO.NET Provider for Sage Intacct solves these issues by supporting powerful smart caching technology that can greatly improve the performance and dramatically reduce application bottlenecks.
Smart Caching
Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart caching creates a persistent local cache database that contains a replica of data retrieved from the remote source. The cache database is small, lightweight, blazing-fast, and it can be shared by multiple connections as persistent storage.
Caching with our ADO.NET Providers is highly configurable, including options for:
- Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically load data into the cache database each time you execute a SELECT query. Each row returned by the query will be inserted or updated as necessary into the corresponding table in the cache database.
- Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache and when it is updated. Explicit caching provides full control over the cache contents by using explicit execution of CACHE statements.
- No Cache - All requests access only live data and no local cache file is created.
This powerful caching functionality increases application performance and allows applications to disconnect and continue limited functioning without writing code for additional local storage and/or data serialization/deserialization.
More information about ADO.NET Provider caching and best caching practices is available in the included help files.
Visual Studio Integration & Server Explorer
Working with the new Sage Intacct ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the Sage Intacct Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.
As an ADO.NET Data Provider, Sage Intacct ADO.NET Provider can be used to access and explore Sage Intacct data directly from the Visual Studio Server Explorer.
It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to Sage Intacct ADO.NET Provider just like connecting to any standard database.
- Add a new Data Connection from the Server Explorer and select the Sage Intacct Data Source
- Configure the basic connection properties to access your Sage Intacct account data.
Explore all of the data available! Sage Intacct ADO.NET Provider makes it easy to access live Sage Intacct data from Visual Studio.
- After configuring the connection, explore the feeds, views, and services provided by the Sage Intacct Data Source.
- These constructs return live Sage Intacct data that developers can work with directly from within Visual Studio!
Developer Integration: Databind to Sage Intacct
Connecting Web, Desktop, and Mobile .NET applications with Sage Intacct is just like working with SQL Server. It is even possible to integrate Sage Intacct ADO.NET Provider into applications without writing code.
Developers are free to access the Sage Intacct ADO.NET Provider in whatever way they like best. Either visually through the Visual Studio Winforms or Webforms designers, or directly through code.
- Developers can connect the Sage Intacct Data Source directly to form components by configuring the object's smart
tags.
- Add a new Data Connection from the Server Explorer and select the Sage Intacct Data Source. Then, select the
feed, view, or services you would like to connect the object to.
Done! It's just like connecting to SQL Server.
- Once the object is bound to the data source, applications can easily interact with Sage Intacct data with full
read/write (CRUD) support.
Popular ADO Videos:
