Skip to main content

Common Errors and FAQs

Project​

Error: Project Already Exists​

If you encounter the error [Autodesk Build Error] [Project Name] already exists, you will need to either:

  1. Link the Record: link the Project to the existing Project in Autodesk Build, or
  2. Check for Duplicates: if you cannot link the Project, it means there is already a Project in your accounting system that links to the Autodesk Project. In this case, you can:
    • Delete or consolidate the duplicate Project in your accounting system,
    • Ignore the duplicate record, or
    • Update the name of the Project name to make it unique.

Error: Invalid State Code for Country​

When syncing Projects, Vendors, or Customers in Autodesk Build, only valid state or province names and ISO 3166-1 alpha-2 country codes are supported. Additionally, the specified state or province must correspond to a valid location within the project's country.

United States​

Below is a list of valid state codes for use in Autodesk Build:

  • AL: Alabama
  • AK: Alaska
  • AZ: Arizona
  • AR: Arkansas
  • CA: California
  • CO: Colorado
  • CT: Connecticut
  • DE: Delaware
  • FL: Florida
  • GA: Georgia
  • HI: Hawaii
  • ID: Idaho
  • IL: Illinois
  • IN: Indiana
  • IA: Iowa
  • KS: Kansas
  • KY: Kentucky
  • LA: Louisiana
  • ME: Maine
  • MD: Maryland
  • MA: Massachusetts
  • MI: Michigan
  • MN: Minnesota
  • MS: Mississippi
  • MO: Missouri
  • MT: Montana
  • NE: Nebraska
  • NV: Nevada
  • NH: New Hampshire
  • NJ: New Jersey
  • NM: New Mexico
  • NY: New York
  • NC: North Carolina
  • ND: North Dakota
  • OH: Ohio
  • OK: Oklahoma
  • OR: Oregon
  • PA: Pennsylvania
  • RI: Rhode Island
  • SC: South Carolina
  • SD: South Dakota
  • TN: Tennessee
  • TX: Texas
  • UT: Utah
  • VT: Vermont
  • VA: Virginia
  • WA: Washington
  • WV: West Virginia
  • WI: Wisconsin
  • WY: Wyoming

Canada​

Below is a list of valid province codes for use in Autodesk Build:

  • AB: Alberta
  • BC: British Columbia
  • MB: Manitoba
  • NB: New Brunswick
  • NL: Newfoundland and Labrador
  • NS: Nova Scotia
  • ON: Ontario
  • PE: Prince Edward Island
  • QC: Quebec
  • SK: Saskatchewan
  • NT: Northwest Territories
  • NU: Nunavut
  • YT: Yukon

Error: NotAllowedException: Not Authorized. Current project is not active.​

This errors is from the Project no longer being marked as Active in Autodesk.

To resolve this error, you can either:

  1. Mark the Project as Active in Autodesk. You can do this by going to Account Admin-->Projects, and selecting the Archived tab. From there, you can select to Restore Projects:

    Projects

  2. Disable Auto-syncs for the Project in Agave. You can do this by going to the Projects tab in the Agave Sync website, and toggling off Automatic Sync for the Project:

    Projects

If you want to apply Project Templates in Autodesk Build as a default, see our guide on setting up Project Templates.

Configuring Autodesk Budget Codes to Match your Accounting System​

You will want to make sure your Autodesk Build Budget Codes is set up to match the structure of your Sub Jobs, Cost Codes, and Cost Types in your Accounting System. We recommend properly configuring this in your Project Template(s) to ensure all Autodesk Projects use the same Budget Code structure.

The following includes a video walk through and guide to properly onfigure your Project Template's Budget Code.

To ensure they match:

  1. In your Project Template, go to the Cost Management module.

Budget Code
  1. Select the gear icon or Settings on the left navigation.

Budget Code
  1. Select the Budget tab, select Add New.

Budget Code

Configuring Sub Jobs​

If you plan to use Sub Jobs, complete the following steps. If you do not, feel free to skip this step.

Note, the following Accounting Systems have the concept of Sub Jobs:

  • Acumatica ("Tasks")
  • Foundation ("Phases")
  • Sage 100 Contractor ("Phases")
  • Sage 300 CRE ("Extras")
  • Sage Intacct
  • Vista

To configure your Sub Job setup:

  1. Press the pencil icon next to Segment 1, and type in Sub Job.

Budget Code
  1. Below Sub Job:
    • For Where, select "Code"
    • For Number of Characters, select "Flexible"
    • For Delimiter, select "Hyphen"

Budget Code

Configuring Cost Codes​

To configure your Cost Code setup:

  1. Press the pencil icon next to Segment 1, and type in Cost Code.

Budget Code
  1. Below Cost Code:
    • For Where, select "Code"
    • For Number of Characters, select "Flexible"
    • For Delimiter, select "Hyphen"

Budget Code

Configuring Cost Types​

To configure your Cost Type setup:

  1. Press the pencil icon next to Segment 2, and type in Cost Type.

  2. Below Cost Type:

    • For Where, select "Code"
    • For Number of Characters, select "Flexible"
    • For Delimiter, select "None"

Budget Code

The type field is required.​

When syncing Projects form Sage 300CRE to Autodesk, we require a project type.

To resolve this error, you can go into the Job Setup > General in Job Cost module in Sage 300CRE, and add a Type there. The type here should be any free form text.

Purchase Order​

How does the General Ledger info sync over?​

For context, Autodesk does not have a General Ledger. All Customers appear to want the General Ledger Account to be specified at the line item-level in Sage 300CRE for Purchase Orders. As a result, we will write the Purchase Order's General Ledger Account using the Line Item's Cost Type's Ledger Account.

How does retention % sync over from Autodesk Build to Sage 300CRE?​

We take the Retention % of Work Completed from Autodesk and sync them as Overall Retention on the Commitment in Sage 300CRE.

Subcontract​

Sage 300 CRE: Subcontract with source_id 'XXX' and id 'XXX' not found​

You will need to enable the CN (Contracts) model in Sage 300 CRE.

How does the General Ledger info sync over?​

For context, Autodesk does not have a General Ledger. All Customers appear to want the General Ledger Account to be specified at the line item-level in Sage 300CRE for Subcontracts. As a result, we will write the Subcontract's General Ledger Account using the Line Item's Cost Type's Ledger Account.

How does retention % sync over from Autodesk Build to Sage 300CRE?​

We take the Retention % of Work Completed from Autodesk and sync them as Overall Retention on the Commitment in Sage 300CRE.

Change Order​

Sage 300 CRE: Subcontract Change Order with source_id 'XXX' and id 'XXX' not found​

Agave currently only supports PJ Change Orders. Check this setting in your project and retry.

Sage 300 CRE Change Orders - Use PJ

Unit Cost Mismatch​

You may encounter an error like "Unit cost mismatch between contract line item 139200 and change order line item -8000.0000" when attempting to sync a Subcontract Change Order to Sage 300 CRE.

For context, Sage 300 CRE has two types of Commitments (i.e. Subcontracts or Purchase Orders):

  1. Lump Sum:
    • Only amount fields exist on the Line Item. In other words, "unit cost" and "quantity" are not set.
    • Subcontracts are typically Lump Sum Commitments.
  2. Unit Price:
    • The amount is determined based on the "unit cost" multiplied by "quantity".
    • Purchase Orders are typically Unit Price Commitments.

For Unit Price Commitments, Sage 300 CRE prohibits modifying the unit cost of an existing Subcontractor Change Order line item. Therefore, Agave Sync returns the "unit cost mismatch" error when you attempt to modify the unit cost for a Unit Price Commitment.

To resolve this error, you will either need to:

  1. Keep the same unit cost as the original Subcontract or Purchase Order and modify the quantity to match the amount, or
  2. Change the Subcontract or Purchase Order to be of type "Lump Sum" (so you can just modify the amount)