Content Center migration

[mat_hijs]

What would be the best way to deal with Content Center Files when migrating to a newer version of Inventor?

At the moment I'm the first and only Inventor user in the company, but more users may come in the future. I'm using Inventor 2024 and I created some custom Content Center Libraries.

By default Inventor will create a separate folder for Content Center Files for each release of Inventor, but I'm wondering how this works when installing a newer version since I believe the parts that have already been placed will have a link to the older release folder.

The second option I see is creating one folder, independent of release. I think the parts should be updated automatically when placing them (if the option is enabled), so you wouldn't have files from an older folder.

What's the best way to approach all this?

[dave.cutting · Accepted solution]

Hi,

These are just my thoughts.

• You should store your all of the files that the content centre generates in a central location. That way you future proof yourself if any other user come in the future.
• Use a common project file this will make sure that all of the users are accessing the same file locations, so the release specific folders don't become an issue either.
• Unless you really feel the urge, there's no need to migrate the generated content centre files up to the latest release. They're placed as normal.
• Also, store your custom content centre file in a central location too.Again everyone will be access the same data. If you're using Vault, it would be worth storing your custom content centre there.

[swalton]

The help pages discuss migrating standard CC libraries here: https://help.autodesk.com/view/INVNTOR/2024/ENU/?guid=GUID-75DD27B5-70EE-47E0-B0A5-0082EA9EB24D

Custom Libraries are discussed here:

https://help.autodesk.com/view/INVNTOR/2024/ENU/?guid=GUID-CEA48D57-577A-4551-BD71-9303AEAEC5DC

[Frederick_Law · Accepted solution]

The Library don't need migration.

The generated file could use migration.

I keep all same Version IV files in same folder: IV2017, IV2023 etc.

That include: Template, CC generated files, Design Data folder, iFeature, iLogic, Macro etc.

All keep all projects in there.

So when updating to 2025, I'll copy the folder and rename it to IV2025.

Project file and Application Setting for 2025 will point all referenced files to that folder.

I'll use task scheduler to migrate files in that folder.

In 4 steps.  First ipt then iam.  Next ipn and then idw.

Migration is done over night.

Only select Folders you need to migrate.  Don't pick Design Data, iFeature etc.

Select "Content Center", Projects you are working on, Custom Library file.

This way, you have an isolated folder of files.  You can keep working on old IV version until everything is done and check before moving to new version.

I do that when new version is released.  Check addins, check if new version has bugs.

Yes, it means I have multiple IV versions installed.  Usually has 3.

If you use Vault, Vault only work on one IV version.  Same version as Vault.