Skip to main content

Common Errors and FAQs

General FAQs​

Are there any particular considerations or best practices we should be aware of when integrating at the top level versus the entity level with Intacct?​

Each Agave sync configuration links one Autodesk Hub with one Sage Intacct Entity.

Both integration approaches—(1) at the top-level entity or (2) at an individual child entity—are viable. However, we would generally recommend integrate at the child-entity level for the following reasons:

  1. If additional entities are added over time (e.g., through acquisitions), they wouldn’t all need to be connected to Autodesk individually.
  2. While filters can be applied at the top level to achieve similar results, managing syncs at the child level provides more control.
  3. Most core objects (e.g., Vendors, Customers) can still be set up at the top-level entity and shared with child entities as needed.

There are two considerations with the child-entity integration approach though:

  1. More Overhead Work: permissions, modules, and settings would need to be managed separately for each entity instead of just at the top level.
  2. Additional Costs: each new sync configuration (i.e., integrating another entity with Autodesk) would incur additional costs from Agave.

Are there any known issues or limitations that could affect the integration's performance or functionality at either level?​

Typically, no major issues arise at either level. However, a top-level entity may contain significantly more data, potentially leading to:

  1. Higher request volume to Intacct.
  2. The need for more filtering, which could slow down requests.

What are costs from Sage Intacct for using Agave Sync?​

You will need to must purchase a separate "Web Services" license, which costs $2,500/yr for 100k total requests per month.

For more details on enabling the Web Services license, see link.