iLogic - Add row to BOM dependent on iProperty

iLogic - Add row to BOM dependent on iProperty

lance_stevens1
Enthusiast Enthusiast
431 Views
3 Replies
Message 1 of 4

iLogic - Add row to BOM dependent on iProperty

lance_stevens1
Enthusiast
Enthusiast

Looking for help with some iLogic code.  I know there's a bunch of post about code for manipulating the BOM with iLogic.  But can't seem to find a post with this specific scenario.

 

Here's our objective:  Looking to add to rows into the BOM in an assembly.

 

 

Here's the setup:

 

The assembly will have 4 custom iProperties.  As follows...

 

Code 1 = YES or NO

 

Code1 QTY = some number

 

Code 2 = YES or NO

 

Code 2 QTY = some number

 

So a user will choose if Code 1 and Code 2 is YES or NO.  And they will manually fill out a Quantity.

 

 

So what I'm looking to do is... if Code 1 and/or Code 2 have a YES... then I want a row added to the BOM that says Code 1 for the name (or Code 2).  At this point, the Quantity would be applied as well.

 

Is this possible?

 

Ultimately, this needs to show up on a Parts List in a Drawing.  But I'd like it on the assembly, so it automatically shows up when a Parts List is pulled.

 

 

I know this could be done with Virtual Components.  But this won't fit the scenario in this particular Engineering/Design department.  These departments use Vault.  We want Code 1 & 2 (and quantities) to show up as properties in Vault.  So engineers can simply find the assembly in Vault and edit the Vault property (we'd obviously create a custom Vault property linked to the custom iProperty).

 

 

Any help would be appreciated!  Thanks so much!

0 Likes
432 Views
3 Replies
Replies (3)
Message 2 of 4

HermJan.Otterman
Advisor
Advisor

you could add a virtual component.

would that be an option for you?

you can do that also with code

If this answers your question then please select "Accept as Solution"
Kudo's are also appreciated Smiley Wink

Succes on your project, and have a nice day

Herm Jan


0 Likes
Message 3 of 4

lance_stevens1
Enthusiast
Enthusiast

Thanks Herm... but my post mentions why virtual components are not a viable solution for their setup.  See below.

 

From my post:

 

I know this could be done with Virtual Components.  But this won't fit the scenario in this particular Engineering/Design department.  These departments use Vault.  We want Code 1 & 2 (and quantities) to show up as properties in Vault.  So engineers can simply find the assembly in Vault and edit the Vault property (we'd obviously create a custom Vault property linked to the custom iProperty).

 

 

 

Any idea what the iLogic code would look like for something like this?

 

 

 

0 Likes
Message 4 of 4

HermJan.Otterman
Advisor
Advisor

ah, sorry for that.

 

If this answers your question then please select "Accept as Solution"
Kudo's are also appreciated Smiley Wink

Succes on your project, and have a nice day

Herm Jan


0 Likes