Ready to get started?

Learn more or sign up for a free trial:

CData Sync

Replicate Epicor Kinetic Data to Multiple Databases



Replicate Epicor Kinetic data to disparate databases with a point-and-click configuration.

Always-on applications rely on automatic failover capabilities and real-time access to data. CData Sync integrates live Epicor Kinetic data into your mirrored databases, always-on cloud databases, and other databases such as your reporting server: Automatically synchronize with remote Epicor Kinetic data from Windows.

Configure Replication Destinations

Using CData Sync, you can replicate Epicor Kinetic data to any number of databases, both cloud-based and on-premises. To add a replication destination, navigate to the Connections tab.

For each destination database:

  1. Click Add Connection.
  2. Select a destination. In this article, we use SQLite.
  3. Enter the necessary connection properties. To replicate Epicor Kinetic to a SQLite database, enter a file path in the Data Source box.
  4. Click Test Connection to ensure that the connection is configured properly.
  5. Click Save Changes.

Configure the Epicor Kinetic Connection

You can configure a connection to Epicor Kinetic from the Connections tab. To add a connection to your Epicor Kinetic account, navigate to the Connections tab.

  1. Click Add Connection.
  2. Select a source (Epicor Kinetic).
  3. Configure the connection properties.

    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.
  4. Click Connect to ensure that the connection is configured properly.
  5. Click Save Changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

Replicate Entire Tables

To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.

Customize Your Replication

You can use a SQL query to customize your replication. The REPLICATE statement is a high-level command that caches and maintains a table in your database. You can define any SELECT query supported by the Epicor Kinetic API. To customize your replication, click Add Custom Query in the Tables section and define the Query Statement.

The statement below caches and incrementally updates a table of Epicor Kinetic data:

REPLICATE Customers;

You can specify a file containing the replication queries you want to use to update a particular database. Separate replication statements with semicolons. The following options are useful if you are replicating multiple Epicor Kinetic accounts into the same database:

  • Use a different table prefix in the REPLICATE SELECT statement:

    REPLICATE PROD_Customers SELECT * FROM Customers;
  • Alternatively, use a different schema:

    REPLICATE PROD.Customers SELECT * FROM Customers;

Schedule Your Replication

In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 10 minutes to once every month.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Epicor Kinetic data to disparate on-premises, cloud-based, and other databases.