Hi there, you can find the rest of the videos on our channel when you search, "iLogic Design Automation" Here is a link to part 3: ruclips.net/video/roYnZCSYRVw/видео.html
If model parameters are changed then, incidentally parts will be also changed, which might be used in another assembly. which consequently changes that assy too, which obviously is not intended. How to deal with this problem ?
Hi Soumyajit, In the situation you described, inventor/vault will recognize any changes and will flag any potential waiting updates. You'll often times see a dialog box when opening up assemblies talking about how "updates are expected," and you have the option to show the changes or not. For simple changes like changing the parameter length of a bar, Inventor is pretty good at making the updates without any harm. But overall it's best to be aware of what changes you are making on a holistic level before committing any check-ins. Otherwise, you also have previous versions of all the parts and assemblies available in vault to fall back on as well.
Where are the next parts of these webinars?
Hi there, you can find the rest of the videos on our channel when you search, "iLogic Design Automation" Here is a link to part 3:
ruclips.net/video/roYnZCSYRVw/видео.html
If model parameters are changed then, incidentally parts will be also changed, which might be used in another assembly. which consequently changes that assy too, which obviously is not intended. How to deal with this problem ?
Hi Soumyajit,
In the situation you described, inventor/vault will recognize any changes and will flag any potential waiting updates. You'll often times see a dialog box when opening up assemblies talking about how "updates are expected," and you have the option to show the changes or not. For simple changes like changing the parameter length of a bar, Inventor is pretty good at making the updates without any harm. But overall it's best to be aware of what changes you are making on a holistic level before committing any check-ins. Otherwise, you also have previous versions of all the parts and assemblies available in vault to fall back on as well.
how do i run the code automatically after i opened the document?
You can try with i-trigger.