Sage Intacct REST Data Targets

Overview

DataBlend supports the following data targets for creating and modifying records.

Journal Entry (Beta)
- Note the REST API uses transaction types "debit" and "credit" so there is no longer a need to use the negative amounts to indicate the debit vs credit.
Project Resources

Configuration

Setting	Required/ Optional	Description
Query	Required	Select the query that will generate the data for this target. See the relevant target type documentation for additional details on what query columns are required for your target.
Query Mode	Required	Choose New unless you have a reason for choosing Latest or Specific.
Credential	Required	Select a Sage Intacct REST Credential from the list.
Entity ID	Optional	By default, DataBlend will authenticate to Intacct at the Top Level of the account. If the account is multi-entity and data should not be loaded to the Top Level, then set an Entity ID in the data target
Object Type	Required	Choose the Sage Intacct REST target type from the drop-down menu.
Action	Required	Each Sage Intacct target will modify a single table in the application in one of four ways: Create Delete Update AutoUpsert
Matching Fields	Required	This field is equivalent to the "Group By" option on the XML version, it is required for the data target.
Continue on Error	Optional	Enable or disable the Continue On Error toggle.

To learn more about Sage Intacct REST API requirements, please visit API Reference.

Advanced

History Retention

History Retention (Days) allows users to decide how long they want the information from their data targets to be stored. This field is optional.

Timeout (seconds)

The Timeout section allows users to determine if they would like to timeout collections taking longer than a set number of seconds to collect data.

Skip If No Records Found

The “Skip if No Records Found” button is used to eliminate sending information to Data Targets unnecessarily. Simply enable the “Skip if No Records Found” toggle. The use of this toggle is optional.

Agent

The Agent drop-down for users to select any agent they have established. This is optional.

Run As

Run As allows users to select from a drop-down list of users to run the Workflow. This is optional. Please note that Run As is only available to Admin users. If a user is set as the Run As and then demoted to a Member, the user which demoted the Run As user will instead be set as the Run As.