Are you an iLogic or an iPart person? Well they’ve each got their place – iLogic certainly allows greater flexibility, whereas iParts just can’t be beaten for catalogues of part numbers for standard parts. But did you know they’re not mutually exclusive? You definitely can’t include embedded iLogic in your iParts, but if you want to incorporate a few cheeky iParts in your iLogic assemblies that’s no problem.
My key tip for this would be some sensible naming for the member names of your iPart. This should allow you to avoid having a very long ‘If’ statement choosing between different iPart members, and should just allow you to concatenate the name of the iPart member you need based on assembly parameters.
Also, whenever you’re switching between a finite number of options, there is always a chance that someone will select an option that isn't available. Therefore, I’ve included a helpful error message, telling the user what iPart members are available, instead of simply telling them they’ve picked one that isn’t permitted.
Watch the video below to find out how this works.
Note: the below video was created by Excitech prior to becoming Symetri in January 2021, following its acquisition by Addnode Group. All Excitech products, services and solutions mentioned in this recording are available through Symetri.
You can download the example iLogic code here.
Author
Luke Davenport
Luke started his career in automotive engine design before moving into consulting and software development. Now with 12 years’ experience working with Autodesk products, he is well placed to meet our customers automation needs with well-tailored .Net applications written with the end-user in mind. He enjoys a consultative approach to software creation – active listening to ensure the optimal solution. These days he is mostly found working on our Sovelia Fusion Manage solutions, serverless web functions, or well-crafted Inventor, Vault, AutoCAD, or Revit apps.
