Sage 300

The Sage 300 connector empowers App Xchange customers to integrate their applications with Sage 300's core financial and operational functions, including General Ledger, Accounts Payable/Receivable, Inventory Control, Order Entry, and Purchase Order.

User Access

To access the developer environment for Sage 300, review the Develop for Sage 300 Documentation page at develop.sage.com.

Engagement and Training

If you would like additional training or to ask for enhancements to this connector, please view the following resources: 

Sage Developer Community

Technical Documentation

To view the technical documentation for this product, you must apply for the Sage 300 Development Partner Program.

Connector Endpoints

The documentation below is an OpenAPI description (OAD) of each module in this connector. Note: This is provided as a quick view of coverage and capabilities. The API and endpoints documented are used internally by the platform and not directly by end users.

• Accounts Payable

• Equipment Control

• General Ledger

• Job Cost

• Payroll

• Project Management

• XML Api

Connection in App Xchange

Create a Sage 300 CRE ODBC Service User

Before you begin: you must be a Sage 300 CRE administrator to complete these steps.

For more information about the steps below, see the Sage 300 CRE Knowledge Base.

Note: App Xchange is only compatible with Sage version 18 or newer. Ensure your instance is fully updated for the best results.

1. In Sage 300 CRE, navigate to Options > Security Administration.

2. Select User Setup.

3. Select Add and create a new user with the settings below.

a. User name: XChangeServiceUser

b. Check Set initial password.

c. Create a secure password. Record this for later.

Note: Only use numbers and letters in your password. Do not include special characters.

d. Uncheck User must change password at next logon.

e. Check Password never expires.

4. Select the Roles tab for this user.

5. Check ODBC Service User.

6. Select the Companies tab for this user.

7. Check the boxes for the companies you want to connect.

8. Select Save Changes.

9. If your company has enabled Security Permissions at the Company, File, or Record level, grant the XChangeServiceUser access to all necessary Roles or Security IDs. For more information, consult the latest version of Sage 300 CRE’s User Guide.

The Sage 300 ODBC service user is created.

Connection Details

This connector has not yet been updated to use a formally defined connection. Details on configuring this connector and providing the credentials needed for integration usage are provided below.

Additional Configuration

• • Real-time Action Processing: This feature should always be enabled for optimal performance. Only disable it if you are advised to do so by support.

Sage 300 Database connection string

Create the Sage 300 Database connection string using info from your initial ERP setup. Insert the appropriate values into each field below, separated by semicolons (no spaces).

• Driver=Timberline Data (This may be different if you customized your Sage 300 install.)

• DBQ=[the path to the Sage 300 company data folder, which is first shown when you log into Sage 300 and select your company directory]

• UID=XChangeServiceUser (Reminder: This user name must exactly match that of the Sage ODBC service user you previously recorded.)

• PWD=[the password created for XChangeServiceUser]

• Add this text at the end of your connection string; it never changes: codepage=1252;dictionarymode=0;standardmode=1;maxcolsupport=1536;shortenames=0;databasetype=1;                                      

For example, Driver=Timberline Data; DBQ=\\SERVERNAME\Timberline Office\Data\COMPANY\; UID=XChangeServiceUser; PWD=Ch@rl!e1978; codepage=1252;dictionarymode=0;standardmode=1;maxcolsupport=1536;shortenames=0;databasetype=1;.

Xml Messaging Configuration

• AddressBookKey: 8826C49B-20E0-44f9-A797-0BE8C4226E1F

• ServiceManagementKey: C7FC4D2C-BBC3-4a0b-B58A-ED2A9CBDF07F

• JobCostTransactionServiceKey: 4DEB77A7-D9CD-4560-A52D-088AF3020D9A

• DataConnectionUrl: Enter the data folder path for your company. This should match your DBQ above.

• GeneralLedgerKey: 71948BDB-E50B-49ce-9893-B4E33460A8D5

• GlDataConnectionUrl: Enter the data folder path for your company. This should match your DBQ above.

• GlTargetsUrl: Enter the data folder path for your company’s GLMessaging.xml file. This is typically either \\SERVERNAME\TIMBERLINE OFFICE\9.5\Shared\Config\RoutingCatalogs\GL\GLMessaging.xml or C:\ProgramData\Sage\SERVERNAME\Timberline Office\9.5\Shared\GLMessaging.xml.

• AccountsPayableKey: 3BC2F783-5D10-480d-8F2D-C66C4B730937

• AddressBookMessageTargets: Enter the data folder path for your company’s ABMessageTargets.xml file. This is typically either \\SERVERNAME\TIMBERLINE OFFICE\9.5\Shared\Config\RoutingCatalogs\AB\ABMessageTargets.xml or C:\ProgramData\Sage\SERVERNAME\Timberline Office\9.5\Shared\ABMessageTargets.xml.

• ApDataConnectionUrl: Enter the data folder path for your company. This should match your DBQ above.

• ApTargetsUrl: Enter the data folder path for your company’s apMessaging.xml file. This is typically either \\SERVERNAME\TIMBERLINE OFFICE\9.5\Shared\Config\RoutingCatalogs\AP\apMessaging.xml or C:\ProgramData\Sage\SERVERNAME\Timberline Office\9.5\Shared\apMessaging.xml.

• User: XChangeServiceUser (Reminder: This user name must exactly match the Sage application user you set up in step 3a of this guide.)

• Password: Enter the password you previously recorded for XChangeServiceUser.

User Support

If you encounter a problem or need support for this connector, please create a ticket at App Xchange Support or email xchange_support@trimble.com.

Was this helpful? Give us feedback.