SOLIDWORKS to Dynamics 365 Finance and Operations Integration

Send

Send to Dynamics 365 Finance, all levels

With the assembly open, choose Send to Dynamics 365 Finance, all levels, on the ERP Integrator tab. The dialog shows one row per item and one column per step: create or update item, release item, BOM header, BOM version and BOM lines.

• The engine assembly and the piston assembly are new here, so both are created and released and get a BOM header and version.
• Bore, crank, conrod and the other parts already exist unchanged and show Update skipped.
• A Failed action list tab collects any step that did not go through.

Result in Dynamics 365

The assembly as a released product

In Dynamics 365 the assembly is a released product with the description taken from the SOLIDWORKS custom property. Product type, subtype, storage and tracking dimension groups and the item model group come from the mapping.

• The mapping says which SOLIDWORKS property fills which Dynamics 365 field.
• Fixed values, such as the storage dimension group, are entered there once.

Result in Dynamics 365

BOM version A, valid from the day of the send

The bill of materials is created with version A, valid from the day it was sent, and lists every component with its quantity and unit. The piston assembly appears as a line, with its own BOM behind it.

Check in SOLIDWORKS

Released product and BOM, checked in the task panes

The ERP Item Details pane shows the released product live from Dynamics 365: item and product number, dimension groups, item model group and the units. The ERP Data pane puts SOLIDWORKS and Dynamics 365 next to each other for the whole structure.

• A green check on every line where the two agree, a red mark where they differ.
• Expand a sub-assembly such as PISTON-ASSY to check its own lines.

Rules and AI

A production type rule, approved before it is applied

Describe the rule in the AI chat: 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 reads the SOLIDWORKS descriptions and the Dynamics 365 fields, writes a plan, and asks before it touches the release-item mapping.

• Allow or Don't run it: the mapping change waits for your answer.
• It matches whole words, so the conrod bearing is not mistaken for a ring.
• The macro is compiled before anything else happens.

Preview

Preview Data, one tab per Dynamics 365 entity

The Preview Data tab runs the new rule on the real assembly and shows what would go to Dynamics 365, per tab: items, BOM lines, BOM headers, BOM versions and release items. On Release Items the cap screw is set to None and the rest to BOM.

• Nothing has been sent at that point.
• Saving the macro and sending stay separate steps.

Questions and search

Look up which parts already exist in Dynamics 365

The chat queries the products and released products and answers in one table: all nine parts exist, and only the cap screw changes once the staged rule is saved and sent. Ask whether the component quantities match, and it compares the assembly with the BOM lines: all eight match.

The chat is not tied to one model:

• Your own API key for Claude, OpenAI, Azure OpenAI or any compatible model.
• Sign in with ChatGPT, or let a coding agent such as Claude or Gemini do the work.
• Or plug in your own assistant through the MCP connector.