Integration
On this page, you can manage asynchronous integrations with third party applications such as Sage Intacct. This page includes a list of objects being processed that you can filter by key (item ID), status, and version. Select a key for details about the object on the line.
You can filter the main list by Finance or Master data.
Use the refresh button to update the list and relevant statuses.
This information displayed in the main list cannot be modified.
Data synchronization
In general, data synchronization works in the background asynchronously. However, there are situations when you can chose to synchronize one or multiple objects.
-
Select one or multiple objects in the grid.
-
A bar displays above the grid with options to
Synchronize: Select this option to synchronize objects that were desynchronized or not integrated and you need to synchronize for the first time.
Force synchronize: Select this option to force a synchronization for objects with an error. If an object is pending, it is already synchronizing and you cannot use this option. -
The grid updates when the new request to synchronize completes. Or, select Refresh to see any status updates.
Statuses
Each object can have one of the following integration statuses.
-
Desynchronized: This object is no longer synchronized with the third party application. Select the icon at the end of the line to view a related message.
-
Error: The synchronization failed; a message might display in the Last message column, or select the icon at the end of the line to view a related message. Remember that master data is synchronized at the top level. You can force synchronization and see if that resolves the error.
-
Not integrated: The object is not integrated with Sage Intacct.
-
Pending: The object is waiting to be synchronized or is processing.
-
Success: The integrated object is synchronized across both solutions.
For finance documents synchronized with Sage Intacct:
If there is a communication error on a line, you can retry the synchronization to see if that resolves the error. The retry is performed at the top or entity level according to the Transaction integration level setting.