Ready to get started?

Download a free trial of the Sage 200 Cmdlets to get started:

 Download Now

Learn more:

Sage 200 Icon Sage 200 Data Cmdlets

An easy-to-use set of PowerShell Cmdlets offering real-time access to Sage 200. The Cmdlets allow users to easily read, write, update, and delete live data - just like working with SQL server.

PowerShell Scripting to Replicate Sage 200 Data to MySQL



Write a simple PowerShell script to replicate Sage 200 data to a MySQL database.

The CData Cmdlets for Sage 200 offer live access to Sage 200 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 Sage 200 and the CData Cmdlets for MySQL in PowerShell to replicate Sage 200 data to a MySQL database.

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

  • Schema: Determines which Sage 200 edition you are connecting to. Specify either StandardUK or ProfessionalUK.
  • Subscription Key: Provides access to the APIs that are used to establish a connection. You will first need to log into the Sage 200 API website and subscribe to the API edition that matches your account. You can do so here: https://developer.columbus.sage.com/docs/services/api/uk. Afterwards, the subscription key may be found in your profile after logging into Sage 200.

Collecting Sage 200 Data

  1. Install the module:

    Install-Module Sage200Cmdlets
  2. Connect to Sage 200:

    $sage200 = Connect-Sage200 -SubscriptionKey $SubscriptionKey -Schema $Schema
  3. Retrieve the data from a specific resource:

    $data = Select-Sage200 -Connection $sage200 -Table "Banks"

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

    $data = Invoke-Sage200 -Connection $sage200 -Query 'SELECT * FROM Banks WHERE Code = @Code' -Params @{'@Code'='12345'}
  4. Save a list of the column names from the returned data.

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

Inserting Sage 200 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 Sage 200 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 Sage 200 resource (Banks) and to exist in the database.

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

You have now replicated your Sage 200 data to a MySQL database. This gives you freedom to work with Sage 200 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 Sage 200 and MySQL in PowerShell, you can pipe command results to perform the replication in a single line:

    Select-Sage200 -Connection $sage200 -Table "Banks" | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Banks" -Columns $columns -Values $values }
  • If you wish to replicate the Sage 200 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-Sage200 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')}