Message 1 of 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello,
I’m experiencing an unexpected issue in Autodesk Inventor 2025 related to volume calculation and rounding via iLogic, which is causing inconsistent results in the BOM.
Context (important)
My workflow is the following:
- I start from a single multibody part (multiple solid bodies in the same IPT)
- These bodies are exported as individual components into an assembly
- The bodies are geometrically identical (modeled from the same dimensions)
- The bodies represent wooden packaging components (see image below for reference)
- These bodies are exported as individual components into an assembly
- Due to symmetry and reuse, those ~50 bodies collapse into ~10 unique BOM items
- In the assembly, I use iLogic to:
- Read the component dimensions
- Build the Part Number from those dimensions
- Force identical components to collapse into a single BOM line item
This works correctly for dimensions and Part Number, but fails for volume, which breaks the BOM unification.
What Inventor reports
For two components that come from identical bodies:
- Physical Properties (for each part):
Volume: 4,500,000.000 mm³ Relative Error: 0.000000%
From the modeling and UI perspective, these parts are literally identical.
What the iLogic code does
In iLogic, I read and convert the volume like this:
Dim vol_cm3 As Double
vol_cm3 = partDoc.ComponentDefinition.MassProperties.Volume ' cm³
Dim vol_m3 As Double
vol_m3 = uom.ConvertUnits(vol_cm3, "cm^3", "m^3")
vol_m3 = Math.Round(vol_m3, 3)
The rounded value is stored as a custom iProperty and used in the BOM.
Unexpected result
After running the rule:
- Component A gets 0.004 m³
- Component B gets 0.005 m³
Even though:
- Both parts were created from the same multibody model
- Both show exactly the same volume in the Physical Properties tab
- Both have zero relative error
As a result, Inventor shows *Varies* for volume in the BOM, which prevents proper item unification.
Why this is a problem
For this workflow:
- These components must be treated as identical in the BOM
- Volume consistency is critical for downstream logic (costing, logistics, reporting)
- The inconsistency is not geometric or modeling-related, but appears to come from how volume is returned/handled by the API
Any clarification or best practice for this scenario would be greatly appreciated.
Solved! Go to Solution.