Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
ward_hanotGZU45
367 Views, 2 Replies

Automatic partname renaming after copy in rules

Hello Inventor people,

 

I starting on the iLogic adventure and I have encounterd my first problem. 

I have created an assembly with 3 parts: Cabine, Dak, Vloer. The assembly is called LUX-Cabine.

I created a form witch handels a couple of parameters. They all work well and ass intended.

Now I want this assemblie be copied because I want to use it for making fast customer drawings.

For Customers we have a specifiek namescheme: 2024-XXXX, where X is the number of the project but it does go up normaly because of internal reasons. 

I copied it using ilogic copy design and design assitant. But the rules don't work anymore because the refrence to the Cabine part and not to the new 2024-XXXX-Cabine. 

 

Example:

Feature.IsActive("Cabine-Start:1", "Z1DOE") = DeurZicht1  

 Cabine-Start should become 2024-XXXX-Cabine. 

Is there a way to either change the rule so that it matches the current partname or another workaround so that the form is useble.

I would prefer to renem the parts to the project. I would not like to have a 100 parts all names Cabine acrose several folders.

Thanks in advance

Hi @ward_hanotGZU45.  It sounds to me like you may just need to 'stabilize' your component browser node names directly within your assembly document.  I am not talking about changing the names of the files, or their Part Numbers, just the names shown within the model browser tree, which usually look something like "Part1:1".  These component names shown in the model browser tree can be changed independently of the files, or their Part Numbers.  Doing this will fix those component names so that they do not change, even when the file name changes, or the Part Number changes.  That way your iLogic rule can still refer to the same components, by the same names, even after the design copy process.

Wesley Crihfield

EESignature

(Not an Autodesk Employee)

In a wierd way that seems to do the trick.