Ready to get started?

Download a free trial of the Sage 300 Data Provider to get started:

 Download Now

Learn more:

Sage 300 Icon Sage 300 ADO.NET Provider

Rapidly create and deploy powerful .NET applications that integrate with Sage 300.

Build an OLAP Cube in SSAS from Sage 300 Data



Establish a connection to Sage 300 data data from SQL Server Analysis Services, and use the Sage 300 Data Provider to build OLAP cubes for use in analytics and reporting.

SQL Server Analysis Services (SSAS) serves as an analytical data engine employed in decision support and business analytics, offering high-level semantic data models for business reports and client applications like Power BI, Excel, Reporting Services reports, and various data visualization tools. When coupled with the CData ADO.NET Provider for Sage 300, you gain the capability to generate cubes from Sage 300 data, facilitating more profound and efficient data analysis.

In this article, we will guide you through the process of developing and deploying a multi-dimensional model of Sage 300 data by creating an Analysis Services project in Visual Studio. To proceed, ensure that you have an accessible SSAS instance and have installed the ADO.NET Provider.

Creating a Data Source for Sage 300

Start by creating a new Analysis Service Multidimensional and Data Mining Project in Visual Studio. Next, create a Data Source for Sage 300 data in the project.

  1. In the Solution Explorer, right-click Data Source and select New Data Source.
  2. Opt to create a data source based on an existing or new connection and click New.
  3. In the Connection Manager, select CData ADO.NET Provider for Sage 300, enter the necessary connection properties, and click Next.

    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.

    When you configure the connection, 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 reports and visualizations.

  4. Set the impersonation method to Inherit and click Next.
  5. Name the data source (CData Sage 300 Source) and click Finish.

Creating a Data Source View

After you create the data source, create the data source view.

  1. In the Solution Explorer, right-click Data Source Views and select New Data Source View.
  2. Select the data source you just created (CData Sage 300 Source) and click Next.
  3. Choose a foreign key match pattern that matches your underlying data source and click Next.
  4. Select Sage 300 tables to add to the view and click Next.
  5. Name the view and click Finish

Based on the foreign key match scheme, relationships in the underlying data will be automatically detected. You can view (and edit) these relationships by double clicking Data Source View.

Note that adding a secondary data source to the Data Source View is not supported. When working with multiple data sources, SSAS requires both sources to support remote queries via OpenRowset which is unavailable in the ADO.NET Provider.

Creating a Cube for Sage 300

The last step before you can process the project and deploy Sage 300 data to SSAS is creating the cubes.

  1. In the Solution Explorer, right-click Cubes and select New Cube
  2. Select "Use existing tables" and click Next.
  3. Select the tables that will be used for measure group tables and click Next.
  4. Select the measures you want to include in the cube and click Next.
  5. Select the dimensions to be created, based on the available tables, and click Next.
  6. Review all of your selections and click Finish.

Process the Project

With the data source, data source view, and cube created, you are ready to deploy the cube to SSAS. To configure the target server and database, right-click the project and select properties. Navigate to deployment and configure the Server and Database properties in the Target section.

After configuring the target server and database, right-click the project and select Process. You may need to build and deploy the project as a part of this step. Once the project is built and deployed, click Run in the Process Database wizard.

Now you have an OLAP cube for Sage 300 data in your SSAS instance, ready to be analyzed, reported, and viewed. Get started with a free, 30-day trial of the CData ADO.NET Provider for Sage 300.