Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to Sage 300 Data Using the Script Function in Claris FileMaker Pro
Use the CData ODBC Driver for Sage 300 and the Script function in FileMaker Pro to connect to Sage 300 and work with Sage 300 data in your FileMaker application.
Claris FileMaker is a low-code database application development tool that enables users to create custom apps for managing and organizing data. It combines a powerful relational database engine with an intuitive interface, allowing both technical and non-technical users to design and deploy applications across desktop, web, and mobile platforms.
In this article, we'll explore how to use the CData ODBC Driver for Sage 300 and FileMaker scripting to connect to Sage 300 data.
Create an ODBC Data Source for Sage 300
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.
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 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 reports and visualizations.
Connect and Sync Sage 300 data with FileMaker Using Scripts
In this section, we walk through the steps to connect live Sage 300 data to FileMaker using the CData ODBC Driver for Sage 300 and the Script function. During the initial import, FileMaker brings in all data from the external data source. From the second import onward, it updates only the data that has changed in the external source (a differential update). You can also replace the data in the current record order and schedule these differential updates for automated syncing.
You can download and install the latest version of FileMaker Pro for your Mac/Windows/Linux systems from this link.
Connect and sync Sage 300 data with FileMaker using scripts
Scripting in FileMaker automates complex tasks and workflows by running a sequence of actions with a single command. By using scripting to integrate with Sage 300, you can automatically connect to, import, update, and replace Sage 300 data within your FileMaker applications, streamlining data management and improving efficiency.
First-time importing and adding Sage 300 data using script
In this section, we'll use scripts to import Sage 300 data into FileMaker by following these steps:
- Open FileMaker Pro. Navigate to Create from the left panel and select Blank > Create.
- Enter a filename of your choice and click Save.
- In the Manage Database window, go to the Tables tab and create or rename the table where you want to display the Sage 300 data.
- In the Fields tab, create and add the fields you want to use in the table.
- In the Relationships tab, add table relationships if there are multiple tables, then click OK.
- To reopen and modify the table structure, go to File > Manage > Database.
- Navigate to Scripts > Script Workspace.
- Select New Script to open a new script workspace.
- From the Steps panel on the right, select Records > Import Records > Insert into Script.
- In the Specify Data Source dropdown, choose ODBC Data.
- Select CData Sage300 Sys from the Select ODBC Data Source window, and click Continue. Enter your Sage 300 credentials and click OK.
- In the Specify ODBC SQL Query dialog, enter the SQL query in the SQL text editor to import the desired Sage 300 data.
- Alternatively, select Query Builder to open the SQL Query Builder window. Choose the target table from the Tables section and relevant columns from the Columns section. Click Insert into SQL Query after each selection to auto-generate the query. You can also manually edit the query using WHERE and ORDER BY clauses or the designated tabs. Click OK to finalize the query.
- Click OK.
- In the Specify import order option, click Specify and enter the Sage 300 credentials.
- In the Specify Import Order window, define the import order for the target fields you added earlier. Select Add between the source and target fields to insert the Sage 300 data as new records in the table. Click Import.
- The script now appears in the workspace. Click Run to execute the script and process the import.
- FileMaker imports the Sage 300 data as a table.














Update or Replace Imported Sage 300 data Using a Script
After importing the Sage 300 data into FileMaker, use scripts to update or replace any changes made in Sage 300 by following this process:
- Go back to the Script Workspace by following the steps mentioned in the earlier section.
- Select the existing script, click the settings button, choose Specify under Specify Import Order, and re-enter the Sage 300 credentials to authenticate.
- In the Specify Import Order window, choose Update between source and target to update the imported Sage 300 data. This updates the target's found set with Sage 300 data values from selected fields when the match fields have the same values. You must define at least one match field in the mapping and select the checkbox Add remaining data as new records. Click Import.
- Alternatively, choose the Replace option instead of Update, based on your use case. This replaces the selected fields in the target's found set with Sage 300 data in the current record order. Click Import.
- FileMaker adds the script to the workspace. Click Run to execute the script and process the import query.
- FileMaker imports the updated or replaced Sage 300 data as a table.




Get Started Today
Download a free 30-day trial of CData ODBC Driver for Sage 300 to integrate Sage 300 data into Claris FileMaker and work with Sage 300 data in your FileMaker applications.
Reach out to our Support Team if you have any questions.