How to Access Live JD Edwards Data in Power Automate Desktop via ODBC

The CData ODBC Driver for JD Edwards enables you to access live JD Edwards data in workflow automation tools like Power Automate. This article shows how to integrate JD Edwards data into a simple workflow, moving JD Edwards data into a CSV file.

Through optimized data processing, CData ODBC Drivers offer unmatched performance for interacting with live JD Edwards data in Microsoft Power Automate. When you issue complex SQL queries from Power Automate to JD Edwards, the driver pushes supported SQL operations, like filters and aggregations, directly to JD Edwards and utilizes the embedded SQL engine to process unsupported operations client-side (e.g. SQL functions and JOIN operations).

Connect to JD Edwards as an ODBC Data Source

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.

The driver connects to JD Edwards through your Application Interface Services (AIS) Server. Set the following connection properties:

• URL: The base HTTPS URL of your AIS Server (e.g., https://jde-ais.example.com:8300).
• User: Your JD Edwards username.
• Password: Your JD Edwards password.
• Environment (optional): The JD Edwards environment to use (e.g., PD920 for production or DV920 for development). If not specified, the AIS Server's default environment is used.
• Role (optional): The JD Edwards role for the session. If not specified, the AIS Server's default role is used.
• DeviceName (optional): An identifier for the connecting device or application, used for auditing and logging on the AIS Server.
• Jasserver (optional): The specific Java Application Server (JAS) instance to route requests through, useful in clustered environments.

Choosing Which Data Is Exposed

JD Edwards organizes tables and business views by System Code, and the driver exposes each System Code as its own schema. Use these properties to control which schemas are available:

• DataModel: One or more ERP modules (comma-separated) whose System Codes are exposed as schemas, or All to expose every System Code in the connected instance. Defaults to FinancialManagement.
• SystemCodes: A comma-separated list of additional System Codes to expose alongside those from DataModel (e.g., 42,43).

When you connect, the driver sends your credentials to the AIS Server to obtain a session token and caches it. The driver requests a new token automatically before the session expires.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing workflows.

Integrate JD Edwards Data into Power Automate Workflows

After configuring the DSN for JD Edwards, you are ready to integrate JD Edwards data into your Power Automate workflows. Open Microsoft Power Automate, add a new flow, and name the flow.

In the flow editor, you can add the actions to connect to JD Edwards, query JD Edwards using SQL, and write the query results to a CSV document.

Add an Open SQL Connection Action

Add an "Open SQL connection" action (Actions -> Database) and configure the properties.

• Connection string: DSN=CData JD Edwards Source

After configuring the action, click Save.

Add an Execute SQL Statement Action

Add an "Execute SQL statement" action (Actions -> Database) and configure the properties.

• Get connection by: SQL connection variable
• SQL connection: %SQLConnection% (the variable from the "Open SQL connection" action above)
• SQL statement: SELECT * FROM AccountsPayable.AccountLedger

After configuring the action, click Save.

Add a Write to CSV File Action

Add a "Write to CSV file" action (Actions -> File) and configure the properties.

• Variable to write to: %QueryResult% (the variable from the "Execute SQL statement" action above)
• File path: set to a file on disk
• Configure Advanced settings as needed.

After configuring the action, click Save.

Add a Close SQL Connection Action

Add a "Close SQL connection" action (Actions -> Database) and configure the properties.

• SQL Connection: %SQLConnection% (the variable from the "Open SQL connection" action above)

After configuring the action, click Save.

Save & Run the Flow

Once you have configured all the actions for the flow, click the disk icon to save the flow. Click the play icon to run the flow.

Now you have a workflow to move JD Edwards data into a CSV file.

With the CData ODBC Driver for JD Edwards, you get live connectivity to JD Edwards data within your Microsoft Power Automate workflows.

Related Power Automate Articles

This article explains how to use the CData ODBC Driver for JD Edwards with Power Automate Desktop. Check out our other articles for more ways to work with Power Automate (Desktop & Online):

• JD Edwards Data in Power Automate Desktop using CData Connect AI
• JD Edwards Data in Power Automate (Online) using CData Connect AI