Ready to get started?

Learn more or sign up for a free trial:

CData Connect Server

Create Apps from Sage 300 Data in Qlik Sense Cloud



Use the CData Connect Server to create an OData API for Sage 300 data and build apps from live Sage 300 data in Qlik Sense Cloud.

Qlik Sense Cloud allows you to create and share data visualizations and interact with information in new ways. The CData Connect Server creates a virtual database for Sage 300 and can be used to generate an OData API (natively consumable in Qlik Sense Cloud) for Sage 300. By pairing Qlik Sense Cloud with the CData Connect Server, you get live connectivity to all of your SaaS and cloud-based Big Data and NoSQL sources — no need to migrate your data or write your integrations. Simply connect to Connect Server from Qlik Sense Cloud as you would any other REST service and get instant, live access to your Sage 300 data.

In this article, we walk through two connections:

  1. Connecting to Sage 300 in Connect Server
  2. Connecting to Connect Server from Qlik Sense Cloud to create a model and build a simple dashboard

Configure Connect Server to Connect to Sage 300

To connect to Sage 300 data from Qlik Sense Cloud, you need to configure Sage 300 access from your Connect Server instance. This means creating a user, connecting to Sage 300, adding OData endpoints, and (optionally) configuring CORS.

Add a Connect Server User

Create a Connect Server User to connect to Sage 300 from Qlik Sense Cloud.

  1. Click Users -> Add
  2. Configure a User
  3. Click Save Changes and make note of the Authtoken for the new user

Connect to Sage 300 from Connect Server

CData Connect Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.

  1. Open Connect Server and click Connections
  2. Select "Sage 300" from Available Data Sources
  3. Enter the necessary authentication properties to connect to Sage 300.

    Sage 300 requires some initial setup in order to communicate over the Sage 300 Web API.

    • Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the option under Security Groups (per each module required).
    • Edit both web.config files in the /Online/Web and /Online/WebApi folders; change the key AllowWebApiAccessForAdmin to true. Restart the webAPI app-pool for the settings to take.
    • Once the user access is configured, click https://server/Sage300WebApi/ to ensure access to the web API.

    Authenticate to Sage 300 using Basic authentication.

    Connect Using Basic Authentication

    You must provide values for the following properties to successfully authenticate to Sage 300. Note that the provider reuses the session opened by Sage 300 using cookies. This means that your credentials are used only on the first request to open the session. After that, cookies returned from Sage 300 are used for authentication.

    • Url: Set this to the url of the server hosting Sage 300. Construct a URL for the Sage 300 Web API as follows: {protocol}://{host-application-path}/v{version}/{tenant}/ For example, http://localhost/Sage300WebApi/v1.0/-/.
    • User: Set this to the username of your account.
    • Password: Set this to the password of your account.
  4. Click Save Changes
  5. Click Privileges -> Add, and add the new user (or an existing user) with the appropriate permissions (SELECT is all that is required for Reveal)

Add Sage 300 OData Endpoints in Connect Server

After connecting to Sage 300, create OData Endpoint for the desired table(s).

  1. Click OData -> Tables -> Add Tables
  2. Select the Sage 300 database
  3. Select the table(s) you wish to work with and click Next
  4. (Optional) Edit the resource to select specific fields and more
  5. Save the settings

(Optional) Configure Cross-Origin Resource Sharing (CORS)

When accessing and connecting to multiple domains from an application such as Ajax, there is a possibility of violating the limitations of cross-site scripting. In that case, configure the CORS settings in OData -> Settings.

  • Enable cross-origin resource sharing (CORS): ON
  • Allow all domains without '*': ON
  • Access-Control-Allow-Methods: GET, PUT, POST, OPTIONS
  • Access-Control-Allow-Headers: Authorization

Save the changes to the settings.

Create a Qlik Sense App from Sage 300 Data

With the connection to Sage 300 and OData endpoints created, we are ready to add Sage 300 data to a Qlik Sense app for visualizations, analytics, reporting, and more.

Create a New App and Upload Data

  1. Log into your Qlik Sense instance and click the button to create a new app
  2. Name and configure the new app and click "Create"
  3. In the workspace, click to open the new app
  4. Click to add data from files and other sources
  5. Select the REST connector and set the configuration properties. For the most part, you will use the default values, with the following exceptions:
    • URL: Set this to the API endpoint for your Sage 300 table, using the @CSV URL parameter to ensure a CSV response (i.e. CONNECT_SERVER_URL/api.rsc/Sage300_OEInvoices?@CSV)
    • Authentication Schema: Set this to "Basic"
    • User Name: Set this to the user name you configured above
    • Password: Set this to the Authtoken for the above user
  6. Click "Create" to query Connect Server for the Sage 300 data
  7. Check "CSV has header" and under "Tables," select "CSV_source"
  8. Select columns and click "Add data"

Generate Insights or Customize Your App

With the data loaded into Qlik Sense, you are ready to begin discovering insights. Click "Generate insights" to let Qlik analyze your data. Otherwise, you can build custom visualizations, reports, and dashboards based on your Sage 300 data.

More Information & Free Trial

Now, you have created a simple but powerful dashboard from live Sage 300 data. For more information on creating OData feeds from Sage 300 (and more than 200 other data sources), visit the Connect Server page. Sign up for a free trial and start working with live Sage 300 data in Qlik Sense Cloud.