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

Adam,

Yes I decided to give it a test and suppressed components don't cause any issues. They can stay whatever material they are in the background because it doesn't affect my BOM.
I agree with you about the question at hand. I am really trying to avoid creating a rule that lists every single part. Even though I would probably only have to do it once, there are hundreds of small parts and that would be very time consuming.
I am very inexperienced with the API or VBA code, I only have a pretty good handle on the default snippets in iLogic so I dont even know of the option to control parts like you described from pieces of their names. That method seems like it would be perfect however I am nervous thinking about it because i anticipate having to rename everything or having to remember this method when I name new parts.
I have thought about this alot and had a new idea. I haven't tested it yet but do you think I could possibly use the very first code mentioned in this thread to control ALL parts material, but instead of inserting that code at my top level assembly could I insert it into each sub-assembly ensuring all material within that sub-assembly is identical? I feel I could then control the parameter within those sub-assemblies from my top level assembly and not worry about EVERYTHING changing to one material type.

Does this sound like a possible idea? It sounds much better than naming every single part since I only have a handful of sub-assemblies.

Thanks
Sandro