Copy assembly in Vault, but updating part references in ilogic rules ??

Copy assembly in Vault, but updating part references in ilogic rules ??

fichri17
Enthusiast Enthusiast
530 Views
5 Replies
Message 1 of 6

Copy assembly in Vault, but updating part references in ilogic rules ??

fichri17
Enthusiast
Enthusiast

So this is a bit troublesome to explain but I hope you will understand....

I have an assembly that "toggles on/off" several parts based on the input in a form.
The problem is that my company uses a unique file name generator, so that when I copy the assembly using COPY DESIGN  in Vault, the rules will (of course) still link to the old part files used in the original assembly.
Do anyone have a workaround for getting the iLogic script to update based on the new generated filenames ??

(I can NOT use generic filenames, has to be unique...)

Hope someone got the idea of what my problem is and can guide me in the right direction.

Br,
Frank

0 Likes
531 Views
5 Replies
Replies (5)
Message 2 of 6

mfoster9TD82
Advocate
Advocate

Could you change the model's DisplayName to something generic and have the iLogic look at that?

0 Likes
Message 3 of 6

fichri17
Enthusiast
Enthusiast

That would probably have fixed the issue.
However, due to company regulations,
this is not an option 🤔 

0 Likes
Message 4 of 6

mfoster9TD82
Advocate
Advocate

The only other thing I can think of if create an iProperty with a value to look for , that will be more resources intensive though as those aren't assessable directly in the partDocument/assemblyDocument object

0 Likes
Message 5 of 6

fichri17
Enthusiast
Enthusiast

Thanks for the tip.
I'll have a look at it and see which impact it will have on the performance, and give a feedback 😉

Br Frank

0 Likes
Message 6 of 6

A.Acheson
Mentor
Mentor

Hi @fichri17 

Can you share the rule your using and what values are changing? Maybe mark those lines changing in a different color or text in the line. 

 

You could perhaps use generic variables in the code and either in a seperate rule or before your generic variables are used populate them with file referencing. Similar to what @mfoster9TD82 suggest but stored not in the part / assembly but in the code itself. Obviously stabilizing the occurrence name would be the best method but if your policy is rigid which really it shouldn't be when it comes to ilogic because you lose alot of the benefits then you have little options. 

 

The alternative is to use ilogic copy design outside vault. I don't use vault but I am surprised there isn't an Integrated version of ilogic copy design from that platform. Maybe other vault users can commented on that. 

If this solved a problem, please click (accept) as solution.‌‌‌‌
Or if this helped you, please, click (like)‌‌
Regards
Alan