![]() |
VOOZH | about |
The CData ODBC Driver for Odoo enables out-of-the-box integration with Microsoft's built-in support for ODBC. The ODBC driver instantly integrates connectivity to the real Odoo data with PowerShell.
You can use the .NET Framework Provider for ODBC built into PowerShell to quickly automate integration tasks like replicating Odoo data to other databases. This article shows how to replicate Odoo 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.
Accessing and integrating live data from Odoo has never been easier with CData. Customers rely on CData connectivity to:
Users frequently integrate Odoo with analytics tools such as Power BI and Qlik Sense, and leverage our tools to replicate Odoo data to databases or data warehouses.
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.
To connect, set the Url to a valid Odoo site, User and Password to the connection details of the user you are connecting with, and Database to the Odoo database.
The code below shows how to use the DSN to initialize the connection to Odoo data in PowerShell:
$conn = New-Object System.Data.Odbc.OdbcConnection $conn.ConnectionString = "DSN=CData Odoo Source x64"
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 " + $res_users $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.
To retrieve Odoo 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 Odoo through the .NET Framework Provider for ODBC:
$sql="SELECT name, email from res_users"
$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[$_]
}
}
$cmd = New-Object System.Data.Odbc.OdbcCommand("UPDATE res_users SET id='1' WHERE Id = @myId", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()
$cmd = New-Object System.Data.Odbc.OdbcCommand("INSERT INTO res_users SET id='1' WHERE Id = @myId", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()
$cmd = New-Object System.Data.Odbc.OdbcCommand("DELETE FROM res_users WHERE Id = @myid", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()
Download a free trial of the Odoo ODBC Driver to get started:
Download NowLearn more:
👁 Odoo IconThe Odoo ERP ODBC Driver is a powerful tool that allows you to connect with live Odoo ERP data, directly from any applications that support ODBC connectivity.
Access Odoo ERP like you would a database - read, write, and update Sales Orders, Purchase Orders, Accounts, etc. through a standard ODBC Driver interface.