Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
Ralf_Krieg
in reply to: leoa.87

Hello

 

Ok, now I can reproduce the error, but have no solution for this.The BOM should export, independent of the active LoD.

 

No, the BOM is not affected by Level of Detail (LoD). LoD is only for reducing used RAM on 32bit systems. So you can't export the BOM of a LoD, cause it doesn't exist. If you want to affect the BOM, you have to set the part/assembly occurrence as "Reference" to "kick it out" the BOM. It would be possible to set this occurrences to reference by an iLogic rule if they are suppressed. The problem is, if they are unsuppressed later, the BOM structure had to change to normal, purchased or inseparable? There's more than one possible choice. In short, not a stable way.

The right way would be to convert the assembly into an iAssembly. There you can define which part to exclude in which version. The change of iAssembly version affects the BOM in the correct way. And you can then define which version to export.


R. Krieg
RKW Solutions
www.rkw-solutions.com