Ready to get started?

Download a free trial of the Epicor Kinetic ODBC Driver to get started:

 Download Now

Learn more:

Epicor Kinetic Icon Epicor Kinetic ODBC Driver

The Epicor Kinetic ODBC Driver is a powerful tool that allows you to connect with live Epicor Kinetic data, directly from any applications that support ODBC connectivity.

Access Epicor Kinetic like you would a database - read, write, and update Sales Orders, Purchase Orders, Accounts, etc. through a standard ODBC Driver interface.

Replicate Epicor Kinetic Data from PowerShell



Write a quick PowerShell script to query Epicor Kinetic data. Use connectivity to the live data to replicate Epicor Kinetic data to SQL Server.



The CData ODBC Driver for Epicor Kinetic enables out-of-the-box integration with Microsoft's built-in support for ODBC. The ODBC driver instantly integrates connectivity to the real Epicor Kinetic data with PowerShell.

You can use the .NET Framework Provider for ODBC built into PowerShell to quickly automate integration tasks like replicating Epicor Kinetic data to other databases. This article shows how to replicate Epicor Kinetic 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.

Create an ODBC Data Source for Epicor Kinetic

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 successfully connect to your ERP instance, you must specify the following connection properties:

  • Url:the URL of the server hosting your ERP instance. For example, https://myserver.EpicorSaaS.com
  • ERPInstance: the name of your ERP instance.
  • User: the username of your account.
  • Password: the password of your account.
  • Service: the service you want to retrieve data from. For example, BaqSvc.

In addition, you may also set the optional connection properties:

  • ApiKey: An optional key that may be required for connection to some services depending on your account configuration.
  • ApiVersion: Defaults to v1. May be set to v2 to use the newer Epicor API.
  • Company: Required if you set the ApiVersion to v2.

Connect to Epicor Kinetic

The code below shows how to use the DSN to initialize the connection to Epicor Kinetic data in PowerShell:

$conn = New-Object System.Data.Odbc.OdbcConnection $conn.ConnectionString = "DSN=CData epicorKinetic Source x64"

Back Up Epicor Kinetic 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 " + $Customers $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 Epicor Kinetic 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 Epicor Kinetic through the .NET Framework Provider for ODBC:

Retrieve Epicor Kinetic Data

$sql="SELECT CustNum, Company from Customers" $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 Epicor Kinetic Data

$cmd = New-Object System.Data.Odbc.OdbcCommand("UPDATE Customers SET CompanyName='CompanyName' WHERE Id = @myId", $conn) $cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH") $cmd.ExecuteNonQuery()

Insert Epicor Kinetic Data

$cmd = New-Object System.Data.Odbc.OdbcCommand("INSERT INTO Customers SET CompanyName='CompanyName' WHERE Id = @myId", $conn) $cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH") $cmd.ExecuteNonQuery()

Delete Epicor Kinetic Data

$cmd = New-Object System.Data.Odbc.OdbcCommand("DELETE FROM Customers WHERE Id = @myid", $conn) $cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH") $cmd.ExecuteNonQuery()