IV 2020.2 - Virtual part - Custom iProperty has no value

[rob]

Scratching my head as I think I have done this before but now seem unable.

I have an assembly with virtual components.  I want to use a Custom iProperty from the assembly as a Custom iProperty in the virtual component.  The assembly Custom iProperty is from a linked assembly parameter.

So in my assembly parameters I have Top_Rail_Width:

Exported so a custom iProperty:

A virtual component in the assembly:

custom iProperty "toprail" in the virtual component:

note it has no value:

I want to use in the Stock Number (should be 'toprail' but you get the idea):

So that it comes out in the parts list:

Any advice on how to get this working as desired?  Thanks!

[sundars]

Hi @rob 

In your second image - you have the iProperties dialog showing that you are modifying an existing field and adding a value field to it.

After adding the value, did you click on the "MODIFY" button? You have to specifically hit modify to accept your new value. Once you do that, the value will be populated below in the list box.

Name = toprail

Type = Text

Value = <Top_Rail_Width>

Click on Modify button to accept new changes

I just tried your workflow and I was able to create a partlists showing the correct information.

Thanks

-Shiva Sundaram

[rob]

Hi Shiva:

Yes, I did.  I'll do it again. RMB on virtual part, iProperties, Custom:

Select toprail:

Select fx:

Click Modify:

Click Apply/OK/Close.

RMB on virtual part, iProperties, Custom, no value:

[sundars]

Hi @rob 

any chance you can send me your model file? I can take a look at it. 

thanks

shiva

[sundars]

Hi @rob

If you want you can email me the Assy file showing the problem directly to

sundars@autodesk.com

Also you are using 2020.2?

Thanks
Shiva

[sundars · Accepted solution]

Hi @rob ,

In this case, you want to use parameters from one component and set it to custom iproperties on a different component. The best way to achieve this is using an iLogic rule because we are spanning across multiple components to read parameters.

To do this

1. Load the iLogic AddIn

2. Create a new Rule and give it a name

3. Insert the following code into the editor

4. Save and Run.

5. It should update the custom iproperties on the target part/virtual component 

In the line below, simply rename the source and target component names and parameter names with your own. This should work for all components.

iProperties.Value("Target_Comp:1", "Custom", "Target_ParamName") = iProperties.Value("Source_Comp:1", "Custom", "Source_ParamName")

Thanks

-Shiva Sundaram