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 →
Replicate Dynamics 365 Data from PowerShell
Write a quick PowerShell script to query Dynamics 365 data. Use connectivity to the live data to replicate Dynamics 365 data to SQL Server.
Getting Started
The CData ODBC Driver for Dynamics 365 enables out-of-the-box integration with Microsoft's built-in support for ODBC. The ODBC driver instantly integrates connectivity to the real Dynamics 365 data with PowerShell.
You can use the .NET Framework Provider for ODBC built into PowerShell to quickly automate integration tasks like replicating Dynamics 365 data to other databases. This article shows how to replicate Dynamics 365 data to SQL Server in 5 lines of code.
You can also write PowerShell code to execute create, read, update, and delete (CRUD) operations. See the examples below.
About Dynamics 365 Data Integration
CData simplifies access and integration of live Microsoft Dynamics 365 data. Our customers leverage CData connectivity to:
- Read and write data in the full Dynamics 365 ecosystem: Sales, Customer Service, Finance & Operations, Marketing, and more.
- Extend the native features of Dynamics CRM with customizable caching and intelligent query aggregation and separation.
- Authenticate securely with Dynamics 365 in a variety of ways, including Azure Active Directory, Azure Managed Service Identity credentials, and Azure Service Principal using either a client secret or a certificate.
- Use SQL stored procedures to manage their Dynamics 365 entities - listing, creating, and removing associations between entities.
CData customers use our Dynamics 365 connectivity solutions for a variety of reasons, whether they're looking to replicate their data into a data warehouse (alongside other data sources)or analyze live Dynamics 365 data from their preferred data tools inside the Microsoft ecosystem (Power BI, Excel, etc.) or with external tools (Tableau, Looker, etc.).
Getting Started
Create an ODBC Data Source for Dynamics 365
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
Edition and OrganizationUrl are required connection properties. The Dynamics 365 connector supports connecting to the following editions: CustomerService, FieldService, FinOpsOnline, FinOpsOnPremise, HumanResources, Marketing, ProjectOperations and Sales.
For Dynamics 365 Business Central, use the separate Dynamics 365 Business Central driver.
OrganizationUrl is the URL to your Dynamics 365 organization. For instance, https://orgcb42e1d0.crm.dynamics.com
Connect to Dynamics 365
The code below shows how to use the DSN to initialize the connection to Dynamics 365 data in PowerShell:
$conn = New-Object System.Data.Odbc.OdbcConnection
$conn.ConnectionString = "DSN=CData Dynamics365 Source x64"
Back Up Dynamics 365 Data to SQL Server
After you enable caching, you can use the code below to replicate data to SQL Server.
Set the following connection properties to configure the caching database:
CacheProvider: The name of the ADO.NET provider. This can be found in the Machine.config for your version of .NET. For example, to configure SQL Server, enter System.Data.SqlClient.
CacheConnection: The connection string of properties required to connect to the database. Below is an example for SQL Server:
Server=localhost;Database=RSB;User Id=sqltest;Password=sqltest;
The SQL query in the example can be used to refresh the entire cached table, including its schema. Any already existing cache is deleted.
$conn.Open()
# Create and execute the SQL Query
$SQL = "CACHE DROP EXISTING SELECT * FROM " + $GoalHeadings
$cmd = New-Object System.Data.Odbc.OdbcCommand($sql,$conn)
$count = $cmd.ExecuteNonQuery()
$conn.Close()
The driver gives you complete control over the caching functionality. See the help documentation for more caching commands and usage examples. See the help documentation for steps to replicate to other databases.
Other Operations
To retrieve Dynamics 365 data in PowerShell, call the Fill method of the OdbcDataAdapter method. To execute data manipulation commands, initialize the OdbcCommand object and then call ExecuteNonQuery. Below are some more examples CRUD commands to Dynamics 365 through the .NET Framework Provider for ODBC:
Retrieve Dynamics 365 Data
$sql="SELECT GoalHeadingId, Name from GoalHeadings"
$da= New-Object System.Data.Odbc.OdbcDataAdapter($sql, $conn)
$dt= New-Object System.Data.DataTable
$da.Fill($dt)
$dt.Rows | foreach {
$dt.Columns | foreach ($col in dt{
Write-Host $1[$_]
}
}
Update Dynamics 365 Data
$cmd = New-Object System.Data.Odbc.OdbcCommand("UPDATE GoalHeadings SET Name='MyAccount' WHERE Id = @myId", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()
Insert Dynamics 365 Data
$cmd = New-Object System.Data.Odbc.OdbcCommand("INSERT INTO GoalHeadings SET Name='MyAccount' WHERE Id = @myId", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()
Delete Dynamics 365 Data
$cmd = New-Object System.Data.Odbc.OdbcCommand("DELETE FROM GoalHeadings WHERE Id = @myid", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()
Ready to get started?
Download a free trial of the Dynamics 365 ODBC Driver to get started:
Download NowLearn more:
Dynamics 365 ODBC Driver
The Dynamics 365 ODBC Driver is a powerful tool that allows you to connect with live data from Dynamics 365, directly from any applications that support ODBC connectivity.
Access Dynamics 365 data like you would a database - read, write, and update Dynamics 365 Leads, Contacts, Opportunities, Accounts, etc. through a standard ODBC Driver interface.
