Ready to get started?

Learn more about the Epicor ERP PowerShell Cmdlets or download a free trial:

Download Now

PowerShell Scripting to Replicate Epicor ERP Data to MySQL

Write a simple PowerShell script to replicate Epicor ERP data to a MySQL database.

The CData Cmdlets for Epicor ERP offer live access to Epicor ERP data from within PowerShell. Using PowerShell scripts, you can easily automate regular tasks like data replication. This article will walk through using the CData Cmdlets for Epicor ERP and the CData Cmdlets for MySQL in PowerShell to replicate Epicor ERP data to a MySQL database.

After obtaining the needed connection properties, accessing Epicor ERP data in PowerShell and preparing for replication consists of four basic steps.

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.

Collecting Epicor ERP Data

  1. Install the module:

    Install-Module EpicorERPCmdlets
  2. Connect to Epicor ERP:

    $epicorerp = Connect-EpicorERP -ervice $ervice -ERPInstance $ERPInstance -URL $URL -User $User -Password $Password
  3. Retrieve the data from a specific resource:

    $data = Select-EpicorERP -Connection $epicorerp -Table "Customers"

    You can also use the Invoke-EpicorERP cmdlet to execute pure SQL-92 statements:

    $data = Invoke-EpicorERP -Connection $epicorerp -Query 'SELECT * FROM Customers WHERE CompanyName = @CompanyName' -Params @{'@CompanyName'='CompanyName'}
  4. Save a list of the column names from the returned data.

    $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name

Inserting Epicor ERP Data into the MySQL Database

With the data and column names collected, you are ready to replicate the data into a MySQL database.

  1. Install the module:

    Install-Module MySQLCmdlets
  2. Connect to MySQL, using the server address and port of the MySQL server, valid user credentials, and a specific database with the table in which the data will be replicated:

    $mysql = Connect-MySQL -User $User -Password $Password -Database $Database -Server $Server -Port $Port
  3. Loop through the Epicor ERP data, store the values, and use the Add-MySQL cmdlet to insert the data into the MySQL database, one row at a time. In this example, the table will need to have the same name as the Epicor ERP resource (Customers) and to exist in the database.

    $data | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Customers" -Columns $columns -Values $values }

You have now replicated your Epicor ERP data to a MySQL database. This gives you freedom to work with Epicor ERP data in the same way that you work with other MySQL tables, whether that is performing analytics, building reports, or other business functions.

Notes

  • Once you have connected to Epicor ERP and MySQL in PowerShell, you can pipe command results to perform the replication in a single line:

    Select-EpicorERP -Connection $epicorerp -Table "Customers" | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Customers" -Columns $columns -Values $values }
  • If you wish to replicate the Epicor ERP data to another database using another PowerShell module, you will want to exclude the Columns, Connection, and Table columns from the data returned by the Select-EpicorERP cmdlet since those columns are used to help pipe data from one CData cmdlet to another:

    $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name | ? {$_ -NotIn @('Columns','Connection','Table')}