Autodesk Inventor to Dynamics 365 Finance & Operations Integration

Send

Released products from one send

With the assembly open, send it to Dynamics 365 from the Inventor ribbon, all levels. INV2ERP collects the iProperties of the assembly and every component below it, runs the company rules, creates the products, releases them to the legal entity, and builds the BOM header, the BOM version and the BOM lines.

• The result dialog has a column for each step: create or update the item, release it, BOM header, BOM version and BOM lines.
• When the dialog reports Process completed, every row reads Created and Released, or Not Applicable where a part has no BOM of its own.

Result in Dynamics 365

BOM version A, valid from the send date

The BOM version for the assembly is created as version A with a from date of the send date. Its lines carry each component's item number, quantity and unit, in the order and structure of the Inventor assembly, with the piston sub-assembly as its own line and its own BOM.

• Released product details show the name and description from Inventor, with the storage dimension group, tracking dimension group and item model group filled from the mapping.
• Those fixed values are set once in the settings, not per send.

Check in Inventor

Differences show up in red

Two panes keep you in Inventor. Show ERP Item Details reads the released product live: item number, product number, dimension groups, item model group and the unit symbols. The ERP data pane compares the whole assembly with Dynamics 365 line by line.

• In the demo the cap screw's description had been changed in Inventor after the send. Its cell turns red, and the tooltip shows both values: Conrod Cap Screw in Dynamics 365, Conrod Cap Screw M6 in Inventor.
• Lines that agree get a green check, so the one that needs a new send is easy to find.

Rules and AI

A production type rule, with your approval

Rules go into a macro, and the AI Macro Chat can write it for you. The request here: parts with screw, ring or pin in the description are bought, so they get no production type; everything else is made from a BOM. The AI checks the field on the released product, writes a short plan, and stops at Needs your approval before it changes the release-item mapping.

• Show what it will send lists the exact mapping change before you choose Allow or Don't run it.
• After approval it adds the rule to the macro and compiles it.

Preview

Release Items previewed on the assembly

The Release Items tab of the preview shows what the next send would write: the cap screw with production type None, every other part and both assemblies with BOM.

Nothing has gone to Dynamics 365 yet. The rule takes effect when you save it and send the assembly again.

Questions and search

Ask Dynamics 365 instead of searching it

Asked whether the component quantities match Dynamics 365, the assistant compared the Inventor BOM with the BOM lines and answered that all eight match. Asked which parts already exist and what production type they have today, it queried the released products and answered in one table: all nine exist, all still BOM, until the new rule is saved and sent.

• Questions only read. The answer ends with: nothing was changed by this check.
• The assistant runs on the AI you choose: your own key for Claude, OpenAI, Azure OpenAI or a compatible model, a ChatGPT sign-in, a coding agent such as Claude or Gemini, or your own assistant through the MCP connector.