Last updated:
Export To Exact Synergy
The Export To Exact Synergy node provides a structured and secure way to send data from a dataflow to Exact Synergy. It enables creating, retrieving, updating, or deleting records within the connected Exact Synergy environment, and supports field-level mapping, controlled execution, and duplicate prevention logic.
The integration works directly with Exact Synergy entities such as Items, Projects, Requests, and other available business objects, and is maintained to ensure compatibility with supported Exact Synergy structures and operations.
The node has two main tabs: Export and Output.
Entity selection
Section titled “Entity selection”At the top of the Export tab, you select the entity (for example Item, Project, or Request) and the operation to perform: None, Create, Retrieve, Update, or Delete. The selected operation determines how the record is processed in Exact Synergy.
Column mapping
Section titled “Column mapping”All available entity fields are listed below the operation section. For each field you can map an incoming value, leave it unmapped, view the field description, and see the field data type (string, number, boolean, date, etc.). Columns are paginated and searchable via the Filter field.
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
Section titled “Configuration”The node requires a configured Exact Synergy connection, including URL, user, password, and domain.
Output
Section titled “Output”The Output tab allows structured response handling:
| Component | Description |
|---|---|
| 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 dataflow. |
The node returns operation status and entity response data.
- Always validate incoming data types before exporting.
- Avoid sending full entity payloads unless necessary.
- Be aware of division-based context when writing data.