Application configuration is an integral activity prior to the process of integration. If your chosen application is SAGE 300, credentials need to be provided for validating the agent. Here you will find the detailed description on how to configure the agents for the application of SAGE300, Troubleshooting issues and the attributes and action.
Pre-requisites for Sage300 Configuration
- Select the application SAGE 300 in the APPS section of the APPSeCONNECT Portal.
- Create and publish a connection in the cloud portal.
- Login to the Agent & Update the Configuration in your On-Premise AEC Agent. You will find your Connection present in the agent. To Know about Agent Configuration, Click here
Note: If you are working with custom connector (per business need), custom touchpoints are needed to be created
Configure the Sage300 Application in the Agent
- Login to the APPSeCONNECT Agent.
- Click on Apps Configurations button in the agent. Choose the APPS.
- You can see the following fields in the Sage 300 configuration window.
a. Base URL: This the Base URL of the users SAGE Application.
b. User Name: The User Name of the application.
c. Password: This is the password of the application, which is being used by the user.
d. Tenant ID: Click For more details regarding the Tenant ID.
e. Company Name: This is the Company database name of the SAGE Application.
Note: If you have any Tenant ID put it into the specified field, otherwise giving Hyphen (-)is mandatory
You can get the Database ID of your organization from More > Common Services > Company Profile
Note: If AEC Agent is not opening after placing the adapter in AEC -> Adapter folder, please unblock the .dll and .pdb file from properties section
ISSUE 1: Some of the basic troubleshooting issue happens even after accurate validation done and the touchpoints do not sync.
“If touchpoints do not sync”, we need to do republish touchpoint and reset cache from portal.appseconnect.com and after that do update configuration from APPSeCONNECT agent.
Note: For Integrating SAGE 300 with WooCommerce,
The APPSeCONNECT Extension is needed to be
uploaded in WooCommerce.
The steps for adding plugins/extensions into WooCommerce is provided here
Attributes and Actions
While defining a connect to an API endpoint in SAGE300, you require clear understanding about the data requirements and endpoint configurations. You can refer to this document to find all the endpoint details of your SAGE300 installation. To define the endpoint in APPSeCONNECT you need Actions and Entities. Actions are specifically targeted for an endpoint while schema is the data needed to execute the API. Here, is the list of some of the pre-packaged API actions defined for you which you can easily plug and play while doing your integrations.
The API Documentation for SAGE300 can be accessed from the SWAGGER Documentation. For accessing the same, Navigate to the “protocol://servername/Sage300WebApi”, where the Protocol is HTTP or HTTPS and the ServerName is the name of the SAGE300 server. For Eg: https://localhost/Sage300WebApi
|Endpoint||Action||Action Type||Schema||UI Path|
|IC/ICItems||IC/ICItems||GET||ICItems||Fetch the updated inventory from Sage 300 and put it into the destination application.|
|IC/ICItems||IC/ICItems||GET||ICItems||Fetch the Products from SAGE 300 and post it to the destination application.|
|OE/OEInvoices||OE/OEinvoices||GET||OEInvoices||Fetch the Invoices from SAGE300 and post it to the Destination Application.|
|OE/OEInvoices||OE/OEOrders||POST||OEOrders||Post orders from Source Application to SAGE 300|
|AR/ARCustomers||AR/ARCustomers||POST||Customers||Post customers from Source Application to SAGE 300.|