Export Exact Synergy
Category: ERP
Version: 1.0
Last updated: March 17, 2026
Author: Any2Info
Description
The Exact Synergy Export Node provides a structured and secure way to send data from the Any2Info DataHub to Exact Synergy.
It enables users to create, retrieve, update, or delete records within the connected Exact Synergy environment. The node supports field-level mapping, controlled execution, and duplicate prevention logic.
The integration is designed to work directly with Exact Synergy entities such as Items, Projects, Requests, and other available business objects. The node is maintained to ensure compatibility with supported Exact Synergy structures and operations.
Property Options
The Exact Synergy Export Node contains two main tabs:
Export
Output
Entity Selection
At the top of the Export tab, you can select:
Entity – For example: Item, Project, Request
Operation – Defines the action performed
Available operations:
None
Create
Retrieve
Update
Delete
The selected operation determines how the record is processed in Exact Synergy.
Column Mapping
Below the operation section, all available entity fields are listed.
For each field you can:
Map an incoming value
Leave it empty (not mapped)
View the field description
See the field data type (string, number, boolean, date, etc.)
Columns are paginated and searchable via the Filter field.

Mapped Only
When Mapped only is enabled: Only fields that have a mapped value are sent to Exact Synergy.
This is recommended for update operations to prevent unintended overwrites.
Configuration Options
The node requires a configured Exact Synergy connection.
This includes:
URL
User
Password
Domain
Output Tab
The Output tab allows structured response handling.
Incoming result
Displays input data from the previous node.
Entity fields
Available response fields from Exact Synergy.
Output mapping
Define which fields are returned to the workflow.
The node returns operation status and entity response data.

Tips & Best Practices
Always validate incoming data types before exporting.
Avoid sending full entity payloads unless necessary.
Be aware of division-based context when writing data
Changelog
1.0
March 17, 2026
Initial documentation version added.
Last updated
Was this helpful?