SOLIDWORKS PDM to Dynamics 365 Finance and Operations Integration

Send

Send to D365 F&O, all levels

Right-click the assembly in the vault view and choose Send to D365 F&O, all levels. The add-in reads the data cards and the complete bill of materials from the vault, applies your rules, creates or updates the products, releases them to the company, and writes the BOM header, the BOM version and its lines. The same send can also be triggered automatically or from a workflow approval.

• The result dialog has a column per step: Create/Update Item, Release Item, BOM Header, BOM Version and BOM lines.
• On a re-send, steps with nothing to change read Update skipped, so you can see exactly what was touched.
• Process completed appears at the top when the last line is written.

Result in Dynamics 365

Released product and BOM version A

In Dynamics 365 the engine assembly is a released product with its description from the vault. BOM version A is valid from the release date and lists each component with its quantity and unit.

• Storage dimension group Ware, tracking dimension group None and item model group FIFO are fixed values from the mapping.
• Inventory, purchase, sales and BOM unit symbols go out in the same send.

Check in PDM

The released product on the ERP Product Details tab

Select a file and the ERP Product Details tab reads the released product live from Dynamics 365: item and product number, storage and tracking dimension groups, item model group and the inventory, purchase, sales and BOM unit symbols.

• Add property and Delete Row choose the attributes the tab shows.
• Save Settings keeps the list for the next file.

Compare

Vault BOM against the Dynamics 365 BOM, row by row

The ERP Data tab lists the vault BOM and Dynamics 365 row by row, with release item, BOM and BOM version details, and a green check where they agree, sub-assembly included.

• Compare with the current BOM or with an older BOM version when BOM versioning is enabled.
• Property differences on first-level children show up, as do changes made in the vault since the last transfer.

Traceability

Transfer history with PDM2ERP

PDM2ERP records every transfer from the vault to Dynamics 365, so you can answer who created which product and when.

• Counts of items created or updated in a chosen period, per user.
• Excel export of the report.
• Log viewer for old logs and a process list with the details of each run.

Rules and AI

A production type rule, with your approval

The rule in the video: 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 assistant looked up the Production type field in D365 and the current macro and mappings, then stopped at a Needs your approval card before replacing the release item mappings.

• Allow or Don't run it, and Show what it will send lists the exact change.
• When the rule was ambiguous it asked: should Conrod Bearing count, since bearing contains ring? The answer is a button, with whole-word matching recommended.

Preview

Release items as they would be sent

The Preview Data tab shows the release items as they would go to Dynamics 365: ProductionType None for the cap screw and BOM for everything else, next to the unit symbols, item model group and dimension groups.

The change stays in the working settings until you save it. Dynamics 365 is not touched by a preview.

Questions and search

Where-used across the vault and Dynamics 365

Ask "Which files in this vault use conrod.sldprt, and which of them already exist in Dynamics 365?" The assistant ran a where-used search in PDM, queried D365 and answered in one table: the engine assembly uses it directly and exists as product and released product; the six drawings do not, which is expected because drawings are not sent as items.

• Asked whether the component quantities match Dynamics 365, it read both BOMs and answered: no differences.
• Pick the model behind it: an API key for Claude, OpenAI, Azure OpenAI or a compatible endpoint, a ChatGPT sign-in, a coding agent such as Claude or Gemini, or your own assistant through the MCP connector.