- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Background:
I'm building a product configurator with iLogic. We have a base model that we Copy Design in the Vault for each new product, and then configure it through iLogic.
In the product, I have one component that is accepting ~10 parameters (dimensions of different plates, enable/disable different features, etc). Additionally the component derives features from other parts of the product, meaning the component will be unique for each product. For example; the overall length of the component, and distance between certain features will always be unique for each product, but common for each instance of the component in one product.
Problem:
If I only had a single instance of the component, it would be easy to modify it through iLogic from the top level assembly. The issue is that there can be 2-10 instances of this component in each product, AND they should all be possible to configure independently (using the ~10 parameters per instance of the component).
Possible solution:
A simple way to solve it would be to copy the component part to 10 different files manually (and then configure and enable/disable the different instances through iLogic). The issue is that when we need to change the base model of the component, we will need to overwrite the other 9 duplicates manually, which can get tricky.
I'm considering automating that process through iLogic, but that would get messy and tricky due to Vault integration.
Question:
Is there a better approach for this type of problem?
Solved! Go to Solution.