Placing an iPart in an assembly, and it prompting you to chose 2 parameters.

[harvey_craig2RCUH]

I would like to create a master (i)Part? that has multiple dependencies on its dimensions. When part is places in assembly,I would like for a prompt to show ask size name, which controls overall length, end length, various diameters etc. And then a second prompt asking required pressure which controls the bore diameter.

What I have tried...

• Creating an iPart, entering all the parameters in the table, placing the component in an assembly and from there selecting the member from the place table. This works but to introduce a second dependency I would have to repeat this table several times for each pressure and corresponding bore size which would work but is not neat, confusing for end user and could become an infinitely long table for parts with more than two dependencies.
• Using ilogic to request dependencies using input list boxes and then produce part. This works at part level but I can't find a trigger to run this rule when the part is placed in the assembly.

I think the second solution is the better one, I just don't know the final step to pull it off. I can't be the first person to be making a master part with multiple parameter dependencies.

Thanks for you help!

Harvey

[WCrihfield · Accepted solution]

Hi @harvey_craig2RCUH.  Have you ever used the 'Place iLogic Component' tool before?  If not, then maybe you can check that out, and see if it would work for you.  Just makes sure you mark the important parameters as 'Key', so that you will be prompted for them upon insertion.  The new file placement thing may not be ideal though, because it wants to place them under the assembly in the file system.

I do not use that system myself, but use something a little different.  Once I have a fully configurable model file, with all the important parameters having been renamed, iLogic forms created and set-up to show, and iLogic rules in place to help drive its design upon user decisions...I then place a copy of that model file in my 'Templates' sub folder.  Then, when I want/need a new variation of it, I just click the 'New' button, select that file from the Templates, then my form pops-up, user changes stuff in the form, and boom.  New variation model document created, and all that is left to do is use Save/SaveAs to write it to disk.  This is not an action upon inserting into an assembly, but is a way to generate the needed model, and file, beforehand, then choose that file for what to insert into my assemblies.

[A.Acheson]

Hi @harvey_craig2RCUH 

Have you tried the find row function for ipart/iassembly using the ilogic API, help page here? You can build in as many parameter checks as you need and it will find the specific ipart row. The parameters info could be preloaded to a configuration form launched from the assembly or if you wanted to source them from the ipart itself that can be done. 

The down side of this is it will be dependant on the ipart being in the assembly and it's occurrence name stabilized. So once it is it can be configured. You could place it by code using its path and configure it before placement as well..it just depends where you want the user to start. 

As Wesley mentioned ilogic place component could work here to connect key parameters to assembly parameters but that can be a semi manual method also. 

[harvey_craig2RCUH]

Hey thanks, the place iLogic component works great for what I need. Currently converting all the iParts I've created back to regular parts and controlling the parameters with iLogic rules. 

Thanks very much for the solution, I've spent most of the day working on this.