Autodesk Vault to Dynamics 365 Supply Chain Management Integration

Send

Release an assembly from the Vault item master

Select the assembly, right-click and choose Send to D365 F&O all levels. AV2ERP reads the item and the full bill of materials, applies your rules and works through Dynamics 365 in the order it needs: create the product, release it, then the BOM header, the BOM version and its lines.

• While it runs, the status line names the item being released in Dynamics 365 Finance and Operations.
• The dialog has a column for each step: Create\Update Item, Release Item, BOM Header, BOM Version and BOM lines. In the demo all four products were Created and Released, and only the assembly needed a BOM.
• Run in background closes the dialog and lets you carry on in Vault while the send finishes.

Result in Dynamics 365

Released products and BOM version A

In Dynamics 365 the four released products are there with their product names from Vault. The bracket assembly has BOM version A, valid from the day it was sent, and the bill of materials lines carry the item number, quantity and unit for each component: 1, 4 and 1 pcs.

• Values that never change per item, such as the storage dimension group, are set once in the field mapping.
• Release details such as the item model group and the inventory, purchase and sales unit symbols go out in the same send.

Check in Vault

The released product, read live inside Vault

ERP Item Details shows the released product from Dynamics 365 on the Vault item: item and product number, storage and tracking dimension groups, item model group and unit symbols. It also answers the plain question of whether a product exists in Dynamics 365 at all.

• You decide which product properties the tab lists.
• The selection is saved, so it does not have to be set up again for each item.

Compare

Vault and Dynamics 365 side by side

The ERP data tab lines up Vault and Dynamics 365 for every BOM line, including the release item details and the BOM id, with a green check where both sides agree. Properties of first-level components are compared too, so a changed description or unit on a child item shows up before the next send.

• Hover a cell to see the ERP value and the Vault value next to each other.
• Untick Use latest BOM to compare the Vault BOM and the Dynamics 365 BOM as of chosen dates instead of today.

Traceability

A record of every Vault-to-ERP transfer

The PDM2ERP reporting tool keeps a complete record of what went from Vault to Dynamics 365. For an audit, or when someone asks why a product changed last week, the answer is in one place.

• Items created or updated in a selected period, grouped by day or month.
• Which users created or updated them.
• Excel export, plus the log viewer and process list for the details of each run.

Rules and AI

A production type rule, written for you

What goes where is set once in the field mapping. The rule in the demo goes further: parts with screw, ring or pin in the Vault description are bought, so they get no production type; everything else is made from a BOM. The assistant checked the current mappings, the macro and the exact Production type column in Dynamics 365, made a plan, and asked before touching the field mapping.

• The approval card says what will change, here the release item mapping rows, and Show what it will send lists the exact rows.
• Allow or Don't run it. Nothing is written until you choose.

Preview

Preview per Dynamics 365 entity before anything is sent

The first preview showed that the rule had not fired yet. The assistant read the log, found why, fixed the macro and previewed again. The Release Items tab of Preview Data then shows the locating pin with Production type None and the other three with BOM. Dynamics 365 has not been touched at this point.

• Preview runs the full processing on the selected Vault item, macro included.
• Items, BOM Lines, BOM Headers, BOM Versions and Release Items each get their own tab, so you check what each Dynamics 365 entity would receive.

Questions and search

Questions answered from Vault and Dynamics 365

Ask whether the component quantities of this assembly match Dynamics 365 and the assistant reads the Vault BOM and BOM BRK-2001_A, version A, from Dynamics 365, then answers: all three match, including the four locating pins.

• Searches combine both systems: find the Vault items with Bracket in the title and say which exist in Dynamics 365 and what production type each has. It searches Vault, queries the ERP and returns one table.
• The rows read from Dynamics 365 are shown with the answer.

Bring your own key for Claude, OpenAI, Azure OpenAI or any compatible model, or keep a subscription you already have: sign in with ChatGPT, use a coding agent such as Claude or Gemini, or connect your own assistant through the MCP connector. The AI proposes; mappings, macros and Dynamics 365 only change after you approve.