SAP Business One ADO.NET Provider
 
ADO.NET
SAP Business One Logo

SAP Business One ADO.NET Provider

SQL-based Access to SAP Business One through ADO.NET for your custom .NET applications and SSAS.

download buy now

Other SAP Technologies

Other SAP Drivers

The SAP Business One ADO.NET Data Provider enables user to easily connect to SAP Business One data from .NET applications. Rapidly create and deploy powerful .NET applications that integrate with SAP Business One data including Accounts, Activities, Orders, Customers, and more!

ADO architecture

SAP Business One .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 SAP Business One data, for real-time data access with the SAP Business One Python Connectors
  • 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 SAP Business One Connector.

Target Service, API

The driver connects to SAP Business One through the Service Layer OData interface. It dynamically surfaces data from the Business One Service Layer root URL (e.g., http://localhost:50000/b1s/v1). The driver supports both on-premise and cloud deployments of SAP Business One versions 9.1, 9.2, 9.3 up to 10.0.

Schema, Data Model

The driver models SAP Business One data as relational tables with metadata dynamically retrieved from the Service Layer. Table definitions are obtained dynamically when connecting, allowing access to all SAP Business One entities as standard database tables. Any changes to metadata are automatically loaded upon reconnection.

Key Objects

Primary objects include Accounts, Activities, Orders, Customers, Vendors, Items, Sales Orders, and Purchase Orders. The driver provides access to all SAP Business One business objects exposed through the Service Layer API.

Operations

Full CRUD operations with comprehensive SQL-92 support including SELECT, INSERT, UPDATE, DELETE. Supports complex operations like JOINs, aggregations, and client-side processing for operations not available server-side. Collaborative query processing with push-down optimization for supported operations.

Authentication

Requires User and Password properties for basic authentication to the SAP Business One Service Layer. Also requires the URL property pointing to the Service Layer root. Supports secure connectivity through modern cryptography including TLS 1.2 and SSL encryption.

Start a 30-day Free Trial Today

SAP Business One ADO.NET Download

See what you can do with SAP Business One ADO.NET provider

SSAS Cube
SSAS Cube

Use SAP Business One from SQL Server Analysis Service (SSAS) multi-dimensional cubes. Keep your analytical data modeling and access to any source including cloud and on-premises.

Custom .NET Application
Custom .NET Application

The SAP Business One ADO.NET Provider allows developers to build applications that connect to SAP Business One using familiar SQL and Entity Framework. Integrate SAP Business One to your mission -critical applications or create easy side-by-side applications.

Reporting & BI
Low-Code Dev Platforms

You can connect from ADO.NET compliant low-code development tools:

Reporting & BI
Reporting Tools

You can connect SAP Business One from .NET-based reporting and analytics tools:

Standard ADO.NET Access to SAPBusinessOne

The SAP Business One ADO.NET Provider offers the most natural way to access SAP Business One data from any .NET application. Simply use SAP Business One Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the SAP Business One 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 SAP Business One 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 SAP Business One Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: SAPBusinessOneConnection, SAPBusinessOneCommand, SAPBusinessOneDataAdapter, SAPBusinessOneDataReader, SAPBusinessOneDataSource, SAPBusinessOneParameter, etc. Because of this you can now access SAP Business One data in an easy, familiar way.

For example:

using (SAPBusinessOneConnection conn = new SAPBusinessOneConnection("...")) {
	string select = "SELECT * FROM Accounts";
	SAPBusinessOneCommand cmd = new SAPBusinessOneCommand(select, conn);
	SAPBusinessOneDataAdapter adapter = new SAPBusinessOneDataAdapter(cmd);
	using (adapter) {
		DataTable table = new DataTable();
		adapter.Fill(table);		
		...
	}
}

More Than Read-Only: Full Update/CRUD Support

SAP Business One 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 SAP Business One Data Provider as easily as interacting with a database table. 

using (SAPBusinessOneConnection connection = new SAPBusinessOneConnection(connectionString)) {
	SAPBusinessOneDataAdapter dataAdapter = new SAPBusinessOneDataAdapter(
	"SELECT Id, Where FROM Accounts", connection);
  
	dataAdapter.UpdateCommand = new SAPBusinessOneCommand(
		"UPDATE Accounts SET Where = @Where " +
		"WHERE Id = @ID", connection);

	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");

	DataTable AccountsTable = new DataTable();
	dataAdapter.Fill(AccountsTable);

	DataRow firstrow = AccountsTable.Rows[0];
	firstrow["Where"] = "New Location";

	dataAdapter.Update(AccountsTable);
}

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:

  1. Network Connections - Slow network connections and latency issues are common in mobile applications.
  2. Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
  3. Large Data - Intentional or unintentional requests for large amounts of data.
  4. Disconnects - Complete loss of network connectivity.

The CData ADO.NET Provider for SAP Business One 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 SAP Business One ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the SAP Business One Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.

As an ADO.NET Data Provider, SAP Business One ADO.NET Provider can be used to access and explore SAP Business One data directly from the Visual Studio Server Explorer.

It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to SAP Business One ADO.NET Provider just like connecting to any standard database.

  • Add a new Data Connection from the Server Explorer and select the SAP Business One Data Source
  • Configure the basic connection properties to access your SAP Business One account data.

Explore all of the data available! SAP Business One ADO.NET Provider makes it easy to access live SAP Business One data from Visual Studio.

  • After configuring the connection, explore the feeds, views, and services provided by the SAP Business One Data Source.
  • These constructs return live SAP Business One data that developers can work with directly from within Visual Studio!

Developer Integration: Databind to SAP Business One

Connecting Web, Desktop, and Mobile .NET applications with SAP Business One is just like working with SQL Server. It is even possible to integrate SAP Business One ADO.NET Provider into applications without writing code.

Developers are free to access the SAP Business One 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 SAP Business One 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 SAP Business One 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 SAP Business One data with full read/write (CRUD) support.

Popular ADO Videos:

Connecting to Live Data from ADO Apps

Download the SAP Business One ADO.NET driver today!

download
buy now