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

Hi! On top of what experts already mentioned, I don't think there is a good workflow using iLogic to drive iAssembly or iPart table. iAssembly/iPart were designed to generate library components (self-sustained, independent, and totally driven by the table). iLogic rule can alter the table but it is no different than you edit the iAssembly/iPart table manually. Like I said, the tables should be clearly defined and should not be altered constantly.

If I understood your particular requirement correctly, you should be using iLogic without editing iAssembly/iPart. You can focus on setting up one variation. Then you use iLogic rule to drive parameter change at all levels. When you have one variation done, use iLogic Design Copy to spawn the variation.

At the moment, I am not aware of a better approach to fulfill your requirements in Inventor.

Many thanks!

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer