Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

So what is inventor doing to your documents; and what is it doing during the opening of components.

First the migration may have had issues resolving the database changes properly, like not chasing all the reference files, leaving links out of whack.  So the given solution would be to let Inventor's engine auto fix it when the file is opened. 

 

Next after the component part is opened what is Inventor doing?  Likely just autorunning the .Update or .Update2 commands as it does on all files where we don't set 'defer updates' every time it opens something.  So to force this via API, get the derived part's definition, go through to its components, get the individual file names, run an open (hidden), update, save, close.  Dissecting derived parts is not something I've done personally, because I haven't dealt much with derived parts in the api (more than creating one).

 

Another thought (because your project is revamping an older one), you may already know well, the iLogic compiler now supports VB.Net code.  You could write in Visual Studio using pure VB.Net, where it is easier to write and test thoroughly, then copy back into iLogic as is.

 

jvj