Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →
The Odoo ADO.NET Data Provider enables user to easily connect to Odoo data from .NET applications. Rapidly create and deploy powerful .NET applications that integrate with Odoo ERP data, including Sales Orders, Purchase Orders, Accounts,, and more!
Odoo
Odoo Connectivity Features
- Fully compatible with Odoo API 8.0+, & Odoo.sh Cloud ERP
- 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 Odoo ERP data, for real-time data access
- 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
Target Service, API
The driver connects to Odoo ERP via XML-RPC API. Open source ERP platform.
Schema, Data Model
Models Odoo modules as tables. Comprehensive ERP data model.
Key Objects
Partners, Products, Sales Orders, Invoices, and Stock. Full ERP suite access.
Operations
CRUD operations through API. Workflow respect. Multi-company support.
Authentication
API key or username/password. Database and URL required.
See what you can do with Odoo ADO.NET provider
Use Odoo 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 Odoo ADO.NET Provider allows developers to build applications that connect to Odoo using familiar SQL and Entity Framework. Integrate Odoo 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 Odoo from .NET-based reporting and analytics tools:
Standard ADO.NET Access to Odoo
The Odoo ADO.NET Provider offers the most natural way to access Odoo data from any .NET application. Simply use Odoo Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Odoo 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 Odoo 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 Odoo Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: OdooConnection, OdooCommand, OdooDataAdapter, OdooDataReader, OdooDataSource, OdooParameter, etc. Because of this you can now access Odoo data in an easy, familiar way.
For example:
using (OdooConnection conn = new OdooConnection("...")) {
string select = "SELECT * FROM SalesOrders";
OdooCommand cmd = new OdooCommand(select, conn);
OdooDataAdapter adapter = new OdooDataAdapter(cmd);
using (adapter) {
DataTable table = new DataTable();
adapter.Fill(table);
...
}
}
More Than Read-Only: Full Update/CRUD Support
Odoo 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 Odoo Data Provider as easily as interacting with a database table.
using (OdooConnection connection = new OdooConnection(connectionString)) {
OdooDataAdapter dataAdapter = new OdooDataAdapter(
"SELECT Id, Where FROM SalesOrders", connection);
dataAdapter.UpdateCommand = new OdooCommand(
"UPDATE SalesOrders SET Where = @Where " +
"WHERE Id = @ID", connection);
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");
DataTable SalesOrdersTable = new DataTable();
dataAdapter.Fill(SalesOrdersTable);
DataRow firstrow = SalesOrdersTable.Rows[0];
firstrow["Where"] = "New Location";
dataAdapter.Update(SalesOrdersTable);
}
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 Odoo 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 Odoo ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the Odoo Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.
As an ADO.NET Data Provider, Odoo ADO.NET Provider can be used to access and explore Odoo ERP data directly from the Visual Studio Server Explorer.
It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to Odoo ADO.NET Provider just like connecting to any standard database.
- Add a new Data Connection from the Server Explorer and select the Odoo ERP Data Source
- Configure the basic connection properties to access your Odoo ERP account data.
Explore all of the data available! Odoo ADO.NET Provider makes it easy to access live Odoo ERP data from Visual Studio.
- After configuring the connection, explore the feeds, views, and services provided by the Odoo ERP Data Source.
- These constructs return live Odoo ERP data that developers can work with directly from within Visual Studio!
Developer Integration: Databind to Odoo
Connecting Web, Desktop, and Mobile .NET applications with Odoo ERP is just like working with SQL Server. It is even possible to integrate Odoo ADO.NET Provider into applications without writing code.
Developers are free to access the Odoo 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 Odoo ERP 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 Odoo ERP 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 Odoo ERP data with full
read/write (CRUD) support.
Popular ADO Videos:
