Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
What would be the best practices for file migration in Upchain when installing a new Inventor version (example: start using Inventor 2024 when Upchain CAD database was done in Inventor 2022). Should we make a minor revision for all the parts that are migrated to make sure they stay migrated?
What should we do with Content Center parts that are released and can't be put in development state? Should we leave them as Inventor 2022 parts? If there is a lot of them in an assembly, won't that cause a performance issue?
This is exactly what happens with all CAD software and with all data management programs.
CAD. Normally, either a program is used to open files sequentially in the background and save them or, as the files are reused, the users are in charge of reviewing them and updating them.
In my opinion, the best thing would be that regardless of the CAD software, you could access the NAS Storage of Upchain and perform the operation from the client's computer to use our own CAD license.
To add to that, CC parts are released automatically on check-in and do not (and can't) be revised to be updated to a new Inventor version. See the last paragraph in Upchain help for CC items.
