Custom Fields - Sage Intacct Data Target Requirements

DataBlend supports sending data into Sage Intacct custom fields for various objects for both the header and detail level. Not all Sage Intacct data targets will support customer fields, please reference the below chart for more details about which objects are supported.

How To:

When sending data into a Sage Intacct custom field, the object ID to be used in the query must have a prefix added to it:

Header level fields will require custom.batch. prepended to the custom field’s object ID.

Detail level fields will require custom.entry. prepended to the custom field’s object ID.

Examples:

• A standard object would look like this: CUSTOMERNAME

• A custom field that is at the header level of the AP Bill object, may have an object ID of VENDOR_INTERNAL_ID.

  • The query in DataBlend should look like this: custom.batch.VENDOR_INTERNAL_ID

Things to Consider:

• Custom fields must be added and exist within Sage Intacct prior to sending data into them from DataBlend

• The data from DataBlend must align with the accepted values of the field

  • Example: If the field is a checkbox, DataBlend must send in true or false, all other values would not be accepted

• Custom Dimensions: These would follow a similar format as custom fields when sending in to the data target (custom.batch.[name] and custom.entry.[name]) but the ID for the dimension is the value to send in. The name may have a prefix like "gldim"; for example, gldimprimarystatus. If at header level, you would send this as custom.batch.gldimprimarystatus. You can collect custom dimensions as you would any other dimension like department or project by searching for the dimension name in the collector object and then excluding RECORDNO from the collected fields (this will cause an error). 

Supported Fields: