Autodesk Vault to Dynamics 365 Business Central Integration

Send

Send an assembly with all its levels

In the Vault item master, select the assembly, right-click and choose AV2ERP > Send to BC all levels. AV2BC reads the item and every level of its bill of materials, applies your company rules and writes the lot to Business Central in one pass. Send to BC on its own sends only the selected item.

• The result dialog has one row per item and one column per step: item, production BOM, BOM version and BOM lines.
• Each cell reads Created, Updated, Created\Updated or Not Applicable. In the demo the three parts only needed an item; the assembly got the item, the production BOM, version A and its lines.
• Anything that fails goes to the Failed action list tab next to it, so you do not have to dig through a log file.

Result in Business Central

A certified production BOM with version A active

The four items arrive with their descriptions from Vault. BRK-2001 gets a production BOM with status Certified and version A as the active version. Each line carries the component number, quantity per and unit of measure from the Vault bill of materials, so two locating pins in Vault is a quantity of 2 on the line.

• Items, production BOM header, BOM version and lines are written in the order Business Central needs to certify the BOM.
• Values that are the same on every send, such as the material, are set once in the field mapping.

Files

Picture, drawing PDF and a link back to Vault

The design goes with the item. On the Business Central item card the picture is the Vault thumbnail, the drawing PDF from Vault is listed under Attachments, and a link in the item's Links opens the same item in Autodesk Vault.

Additional actions

Create a routing from the same right-click menu

Choose Create routing on an assembly and AV2BC first shows the routing header and its operation lines in a dialog. Click Create\Update and the routing is in Business Central: operation 10 on work center 100, with its setup and run times.

• The dialog reports a transfer status per line, the same way the send dialog does.
• The demo menu also has Create Item UOM, Create Item Category, Create routing header and Add Vault link, each with an Update counterpart. Which actions appear is part of your configuration.

Check in Vault

Business Central item properties inside Vault

The ERP Item Details tab reads the item live from Business Central, so you see whether a Vault item already exists in the ERP, and with which values, without opening Business Central.

• Choose which item properties the tab shows.
• Save the layout once and every user gets the same view on the next item.

Check in Vault

Preview the Business Central BOM, including older versions

The ERP BOM Details tab lists the production BOM lines as Business Central has them, filtered by BOM status and date. With BOM versioning switched on in Business Central, older versions can be previewed as well as the current one.

• Pick the ERP BOM columns that matter to you.
• The column layout is saved for the next preview.

Compare

Compare the Vault BOM with the Business Central BOM

The ERP data tab puts the Vault BOM and the Business Central BOM side by side, with a green check on every row that agrees and a red cell where it does not. In the demo the locating pin quantity was changed to 4 in Vault while Business Central still had 2; hovering the red cell shows both values.

• Item fields of first-level components, BOM lines, the BOM header and the BOM version are compared, not only quantities.
• Untick Use latest BOM to compare as of a date, with one date for Vault and one for Business Central. On 10 March the sub-assembly in Vault was still revision A, without the part Business Central already listed; on today's date both sides agree.

Traceability

See what was sent, by whom and when

The PDM2ERP reporting tool keeps track of everything sent from Vault to Business Central, for the audit trail and for finding the send that went wrong.

• Number of items created or updated in a chosen period, and by which user.
• Reports export to Excel.
• The log viewer and the process list hold the details of past runs for error investigation.

Rules and AI

Company rules written in plain language

The field mapping decides which Vault property fills which Business Central field. Rules that go further live in a macro, and the AI Macro Generator tab in Vault writes that macro with you. The request in the demo: items in the Purchased category in Vault get Replenishment System Purchase, everything else Prod. Order.

• The assistant first reads the current mappings, the macro, the Business Central field list and the Vault category property, and shows its plan as a checklist.
• Before it changes the field mapping it stops at an Allow / Don't run it prompt that names the mapping rows it will replace.
• It writes the macro, checks that it compiles and runs Preview on the real assembly: the locating pin comes out as Purchase, the rest as Prod. Order.
• Nothing has been sent at that point. Save and Send to ERP stay your decision.

Questions and search

Ask about Vault and Business Central in the same chat

Asked whether the component quantities of the assembly match Business Central, the assistant read the Vault BOM and the production BOM lines from Business Central and answered with a table: the locating pin is 4 in Vault and 2 in Business Central, the other two match.

• The rows it read from Business Central are shown above the answer, so you can see what it is based on.
• Searches across both systems: find the Vault items with Bracket in the title and check which exist in Business Central, answered in one table.
• Questions about Vault itself, such as whether any Vault jobs failed in the last seven days.

The AI is yours to pick in AI Settings: your own key for Claude, OpenAI, Azure OpenAI or another OpenAI-compatible model, a ChatGPT sign-in, a coding agent such as Claude or Gemini, or your own assistant through the MCP connector.