Dynamics 365 ADO.NET Provider
SQL-based Access to Dynamics 365 through ADO.NET for your custom .NET applications and SSAS.
download buy nowOther Microsoft Dynamics Technologies
Other Microsoft Dynamics Drivers
-
-
Microsoft Dynamics CRM
learn more » -
Microsoft Dynamics NAV
learn more »
The Dynamics 365 ADO.NET Data Provider enables user to easily connect to Dynamics 365 data from .NET applications. Rapidly create and deploy powerful .NET applications that integrate with Dynamics 365.
Dynamics 365
Dynamics 365 .NET Connectivity Features
- SQL access to the Dynamics 365 ecosystem, including Sales, Customer Service, Finance & Operations, Marketing, and more.
- 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 Microsoft Dynamics 365 data, for real-time data access with the Microsoft Dynamics 365 ODBC Driver
- 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 Dynamics 365 Connector.
Target Service, API
The Microsoft Dynamics 365 driver supports connecting to the following editions of Microsoft Dynamics 365; CustomerService, FieldService, FinOpsOnline(Default), FinOpsOnPremise, HumanResources, Marketing, ProjectOperations, and Sales.
Schema, Data Model
The driver models Microsoft Dynamics 365 data in relational tables, views, and stored procedures. The table definitions are dynamically obtained from the Microsoft Dynamics 365 OData service when you connect.Any changes to the metadata, such as new or removed columns, or changes in data type, are automatically loaded when you reconnect.
Key Objects
Core CRM Entities such as Account, Contact, Lead. Customer Service Entities, such as Case, Knowledge Article and many more.
Operations
The driver supports SELECT, INSERT, UPDATE, DELETE, CACHE, and many other SQL operations. You can also use Stored Procedures such as CreateSchema, CreateAssociation, and EnableChangeTracking.
Authentication
AzureAD performs Azure ActiveDirectory (user-based)( OAuth authentication. In addition, the driver provide AzureMSI, AzureServicePrincipal, and AzureServicePrincipalCert.
See what you can do with Dynamics 365 ADO.NET provider
Use Dynamics 365 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 Dynamics 365 ADO.NET Provider allows developers to build applications that connect to Dynamics 365 using familiar SQL and Entity Framework. Integrate Dynamics 365 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 Dynamics 365 from .NET-based reporting and analytics tools:
Standard ADO.NET Access to Dynamics365
The Dynamics 365 ADO.NET Provider offers the most natural way to access Dynamics 365 data from any .NET application. Simply use Dynamics 365 Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Dynamics 365 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 Dynamics 365 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 Dynamics 365 Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: Dynamics365Connection, Dynamics365Command, Dynamics365DataAdapter, Dynamics365DataReader, Dynamics365DataSource, Dynamics365Parameter, etc. Because of this you can now access Dynamics 365 data in an easy, familiar way.
For example:
using (Dynamics365Connection conn = new Dynamics365Connection("...")) {
string select = "SELECT * FROM Leads";
Dynamics365Command cmd = new Dynamics365Command(select, conn);
Dynamics365DataAdapter adapter = new Dynamics365DataAdapter(cmd);
using (adapter) {
DataTable table = new DataTable();
adapter.Fill(table);
...
}
}
More Than Read-Only: Full Update/CRUD Support
Dynamics 365 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 Dynamics 365 Data Provider as easily as interacting with a database table.
using (Dynamics365Connection connection = new Dynamics365Connection(connectionString)) {
Dynamics365DataAdapter dataAdapter = new Dynamics365DataAdapter(
"SELECT Id, Where FROM Leads", connection);
dataAdapter.UpdateCommand = new Dynamics365Command(
"UPDATE Leads SET Where = @Where " +
"WHERE Id = @ID", connection);
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");
DataTable LeadsTable = new DataTable();
dataAdapter.Fill(LeadsTable);
DataRow firstrow = LeadsTable.Rows[0];
firstrow["Where"] = "New Location";
dataAdapter.Update(LeadsTable);
}
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 Dynamics 365 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 Dynamics 365 ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the Dynamics 365 Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.
As an ADO.NET Data Provider, Dynamics 365 ADO.NET Provider can be used to access and explore Microsoft Dynamics 365 data directly from the Visual Studio Server Explorer.
It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to Dynamics 365 ADO.NET Provider just like connecting to any standard database.
- Add a new Data Connection from the Server Explorer and select the Microsoft Dynamics 365 Data Source
- Configure the basic connection properties to access your Microsoft Dynamics 365 account data.
Explore all of the data available! Dynamics 365 ADO.NET Provider makes it easy to access live Microsoft Dynamics 365 data from Visual Studio.
- After configuring the connection, explore the feeds, views, and services provided by the Microsoft Dynamics 365 Data Source.
- These constructs return live Microsoft Dynamics 365 data that developers can work with directly from within Visual Studio!
Developer Integration: Databind to Dynamics 365
Connecting Web, Desktop, and Mobile .NET applications with Microsoft Dynamics 365 is just like working with SQL Server. It is even possible to integrate Dynamics 365 ADO.NET Provider into applications without writing code.
Developers are free to access the Dynamics 365 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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 data with full
read/write (CRUD) support.
Popular ADO Videos:
