- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi @wfajber. Good point. That's mainly what I have pretty much always done. I knew that the 'level of detail' representations (before ModelStates) were originally created with performance issues in mind, because they primarily record which components in an assembly are suppressed, and suppressing components 'unloads' them from Inventor's session memory, which increases performance. However, many over the years have adopted the use of suppressing components as a means of controlling BOM quantities. After some initial dabbling/testing with that process, and finding out how restrictive their use was to many of my other processes, I have chosen since then to use 'design view representations', component visibility, and the BOMStructure to help control BOM/PartsList related issues, which has worked just fine for me. However, our assembly BOM's are not directly exported/translated into any sort of ERP system (at this time), and we make more use of drawing PartsLists than we do of the assembly's BOM directly. Plus we use a lot of automation tools, where others may not. So I certainly do not fault or discourage any specific way of doing things, because there are a vast array of needs and scenarios out there that require all sorts of different solutions.
Wesley Crihfield
(Not an Autodesk Employee)