Provides integration with Sage 200 Evolution through the Sage Evolution SDK and direct SQL Server database connections.
0.0.0.1 - Initial release.
0.0.0.13 - Repair project file SDK version reference.
0.0.0.17 - Fixed template returns and runtime error handling.
0.0.0.20 - Split invoke methods.
0.0.0.23 - Overhaul to new standard.
0.1.0.25 - Added Run Anywhere Cluster support.
0.1.0.31 - Added multi-version Sage Evolution SDK support.
0.1.1.5 - Added Sage Evolution 12 support and standardized mutation responses.
Use the Connection to configure the Sage company and common SQL Server databases.
| Property |
Type |
Description |
Server |
String |
The SQL Server instance that hosts the Evolution company database. |
Database |
String |
The Evolution company database name. |
Username |
String |
The SQL username for the company database when UseWinAuth is false. |
Password |
Masked |
The SQL password for Username. |
UseWinAuth |
Boolean |
Set to true to use Windows authentication for the company database. |
CommonDbServer |
String |
The SQL Server instance that hosts the common database. This is typically the same server as the company database. |
CommonDbDatabase |
String |
The Evolution common database name. This is typically EvolutionCommon. |
CommonDbUsername |
String |
The SQL username for the common database when CommonDbUseWinAuth is false. |
CommonDbPassword |
Masked |
The SQL password for CommonDbUsername. |
CommonDbUseWinAuth |
Boolean |
Set to true to use Windows authentication for the common database. |
Branch Id |
Integer |
Optional. Use this to target a specific Sage branch. |
- Ensure the selected Flowgear Cluster can reach the Sage 200 Evolution SQL Server.
- If the SQL Server is behind a firewall, allow the Flowgear tenant or selected Cluster IP address.
- Configure both the company database and common database settings. When Windows authentication is disabled, the matching username and password Properties are required.
- The Node reads the Sage application version from the company database and selects the matching embedded SDK. Sage Evolution 7, 8, and 9 use the 9.20 SDK; version 10 uses the 10.1 SDK; version 11 uses the 11 SDK; and version 12 uses the 12 SDK.
Use the Node templates to populate DocumentType and the Request schema for the selected Sage document type.
Creates a Sage document. This method supports InventoryItem, ApPurchaseOrders, ArSalesOrders, ApReturns, and ArCreditNotes.
| Parameter |
Type |
Description |
Connection |
Connection |
The Sage 200 Evolution Connection profile. |
DocumentType |
Dropdown |
The type of document to create. Select a document type supported by this method. |
Request |
Array |
The document payload. Select a template to populate the schema. |
| Return |
Type |
Description |
Response |
Array |
One processed result row for each supplied document. |
Updates a Sage document. This method supports InventoryItem, ApPurchaseOrders, ArSalesOrders, ApReturns, and ArCreditNotes.
| Parameter |
Type |
Description |
Connection |
Connection |
The Sage 200 Evolution Connection profile. |
DocumentType |
Dropdown |
The type of document to update. Select a document type supported by this method. |
Request |
Array |
The document payload. Select a template to populate the schema. |
| Return |
Type |
Description |
Response |
Array |
One processed result row for each supplied document. |
Completes a purchase order. This method supports ApPurchaseOrders.
| Parameter |
Type |
Description |
Connection |
Connection |
The Sage 200 Evolution Connection profile. |
DocumentType |
Dropdown |
The document type to complete. Use ApPurchaseOrders. |
Request |
Array |
The purchase order payload. Include DocumentID or OrderNo to identify the existing purchase order. |
| Return |
Type |
Description |
Response |
Array |
One processed result row for each supplied purchase order. |
Processes a sales order. This method supports ArSalesOrders.
| Parameter |
Type |
Description |
Connection |
Connection |
The Sage 200 Evolution Connection profile. |
DocumentType |
Dropdown |
The document type to process. Use ArSalesOrders. |
Request |
Array |
The sales order payload. Include DocumentID or OrderNo to identify the existing sales order. |
| Return |
Type |
Description |
Response |
Array |
One processed result row for each supplied sales order. |
Each Request item must contain one Sage document. The Node returns one detached response row per item and adds a nested Flowgear object containing IsSuccess, Message, and a copy of the original input under Request. Nested Content values are excluded from the request copy.
| DocumentType |
Sage document |
Supported methods |
InventoryItem |
Inventory item |
Create, Update |
ApPurchaseOrders |
Purchase order |
Create, Update, Complete |
ArSalesOrders |
Sales order |
Create, Update, Process |
ApReturns |
Supplier return |
Create, Update |
ArCreditNotes |
Credit note |
Create, Update |
ProcessAllOrNone is not applied. The Node processes documents one at a time.