Ready to get started?

Learn more about the CData SSIS Components for Sage 300 or download a free trial:

Download Now

Export Data from SQL Server to Sage 300 through SSIS

Easily push SQL Server data to Sage 300 using the CData SSIS Tasks for Sage 300.

SQL Server databases are commonly used to store enterprise records. It is often necessary to move this data to other locations. The CData SSIS Task for Sage 300 allows you to easily transfer Sage 300 data. In this article you will export data from SQL Server to Sage 300.

Add Source and Destination Components

To get started, add a new ADO.NET Source control and a new Sage 300 Destination control to the data flow task.

Configure the ADO.NET Source

Follow the steps below to specify properties required to connect to the SQL Server instance.

  1. Open the ADO.NET Source and add a new connection. Enter your server and database information here.
  2. In the Data access mode menu, select "Table or view" and select the table or view to export into Sage 300.
  3. Close the ADO NET Source wizard and connect it to the destination component.

Create a New Connection Manager for Sage 300

Follow the steps below to set required connection properties in the Connection Manager.

  1. Create a new connection manager: In the Connection Manager window, right-click and then click New Connection. The Add SSIS Connection Manager dialog is displayed.
  2. Select CData Sage300 Connection Manager in the menu.
  3. Configure the connection properties.

    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.

Configure the Sage 300 Destination

In the destination component Connection Manager, define mappings from the SQL Server source table into the Sage 300 destination table and the action you want to perform on the Sage 300 data. In this article, you will insert OEInvoices entities to Sage 300.

  1. Double-click the Sage 300 destination to open the destination component editor.
  2. In the Connection Managers tab, select the connection manager previously created.
  3. In the Use a Table, menu, select OEInvoices. In the Action menu, select Insert.
  4. On the Column Mappings tab, configure the mappings from the input columns to the destination columns.

Run the Project

You can now run the project. After the SSIS Task has finished executing, data from your SQL table will be exported to the chosen table.