CAD BOM synchronization fails across multiple projects in program management module

PLM Aras Innovator
, , , , , , , ,
1

We’re experiencing BOM synchronization failures when updating item revisions through the SolidWorks connector in our portfolio management rollout. The connector successfully imports the initial assembly structure, but subsequent revision updates fail with a generic “synchronization error” message.

I’ve checked the connector logs and see revision mapping issues between SolidWorks and Aras. The BOM import job configuration seems to handle new items fine but struggles with revision updates. Here’s the error from the log:


<Error>Revision mismatch: SW_Rev='B' mapped to Aras_Rev='A'
BOM job failed at item: ASSY-2401-15
</Error>

This is blocking our project rollout as we can’t maintain synchronized BOMs across the portfolio. Has anyone dealt with revision mapping configuration in the SolidWorks connector for portfolio scenarios?

2

Auto-mapping is definitely your issue. For portfolio management, you need explicit revision mappings because different projects might use different revision schemes. The connector can’t guess which Aras revision corresponds to which SolidWorks revision when you have multiple active projects with different versioning standards.

3

Thanks for the responses. I checked the connector settings and found the revision mapping section. Currently it’s set to auto-map, which I think is causing the problem. Should I create explicit mappings for each revision level? Also, how does this interact with the portfolio structure - do I need different mappings per portfolio project?

4

Here’s what you need to check for portfolio BOM synchronization:

1. SolidWorks-Aras Revision Mapping: Open your connector configuration file and define explicit revision mappings. Replace auto-map with a mapping table:

<RevisionMap>
  <Mapping SW="A" Aras="A" />
  <Mapping SW="B" Aras="B" />
  <Mapping SW="C" Aras="C" />
</RevisionMap>

2. BOM Import Job Configuration: Modify your import job to include revision validation. The job needs to check existing revisions before creating new ones. Add a pre-processing step that queries the current revision state and determines the correct next revision based on your mapping.

3. Connector Log Analysis: Your error shows the connector is receiving revision ‘B’ from SolidWorks but finding revision ‘A’ in Aras. This means either:

  • The previous revision update didn’t complete successfully
  • Your import job is creating items without properly incrementing revisions
  • The portfolio project has a different revision sequence than expected

For portfolio scenarios, I recommend configuring project-specific import jobs with their own revision mapping rules. This prevents cross-contamination between projects with different versioning standards.

Additional Configuration: Enable detailed logging in the connector to track revision progression:

  • Set log level to DEBUG in connector.config
  • Monitor the BOM_Import_Log table in Aras
  • Verify that each revision update creates a proper revision history entry

The connector needs to understand that portfolio items may have complex revision relationships. Make sure your import job configuration includes proper parent-child revision handling for assemblies.

Test this with a single assembly first before rolling out to the full portfolio. Once you verify revision updates work correctly for one project, you can replicate the configuration across your portfolio structure.