Redash is a collaboration tool that lets you query, visualize, and share your data. When paired with
CData Connect AI, Redash gets access to live Epicor Kinetic data. This article demonstrates how to connect to Epicor Kinetic
using Connect AI and work with live Epicor Kinetic data in Redash.
CData Connect AI provides a pure SQL Server interface for Epicor Kinetic, allowing you to query data from
Epicor Kinetic without replicating the data to a natively supported database.
Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations
(filters, JOINs, etc.) directly to Epicor Kinetic, leveraging server-side processing to return the
requested Epicor Kinetic data quickly.
Configure Epicor Kinetic Connectivity for Redash
Connectivity to Epicor Kinetic from Redash is made possible through CData Connect AI. To work with Epicor Kinetic data in Redash, we start by creating and configuring a Epicor Kinetic connection.
-
Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a Connection
- Select "Epicor Kinetic" from the Add Connection panel
👁 Selecting a data source
-
Enter the necessary authentication properties to connect to Epicor Kinetic.
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.
👁 Configuring a connection (Salesforce is shown)
-
Click Save & Test
-
Navigate to the Permissions tab in the Add Epicor Kinetic Connection page and update the User-based permissions.
👁 Updating permissions
Add a Personal Access Token
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
-
Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
-
On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
👁 Creating a new PAT
-
The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
With the connection configured and a PAT generated, you are ready to connect to Epicor Kinetic data from Redash.
Connect to Epicor Kinetic from Redash using Connect AI
To establish a connection from Redash to CData Connect AI using the Virtual SQL Server, follow these steps:
- Log into Redash.
- Click the settings widget on the top right.
- Click New Data Source.
- Select Microsoft SQL Server as the Data Source Type.
-
On the configuration tab, set the following properties:
- Database Name: enter the Connection Name of the CData Connect AI data source you want to connect to (for example, Salesforce1).
- Server: enter the virtual SQL Server host name (tds.cdata.com)
- User: enter your CData Connect AI username. This is displayed in the top-right corner of the CData Connect AI interface. For example, [email protected].
- Password: enter the PAT you generated on the Settings page.
- Port: enter 14333
👁 Configuring the connection to Connect AI from Redash.
- Click Create.
- Click Test Connection to ensure that the connection is configured properly.
You can now work with live Epicor Kinetic data in Redash.
Get CData Connect AI
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Redash,
try CData Connect AI today!
