Migration Options While Saving

[dan_butler_komatsu]

When opening up an assembly, part, drawing, and etc., and upon save the data, we often get models that have been migrated to the latest release.  It would be greatly helpful to do some behind the scene work to migrate these from this dialogue box on the spot by:

1) changing the state from released, or obsolete, or etc to work in process

2) check out the models

2) save the models in their migrated state

3) Check the models back in

4) Return the models back to their original release status

Some advantages:

You are only migrating what needs migrated for the current drawing or assembly that you are in and it is done on the spot.

You don't have to do a special migration task.

Everything you need will be migrated.

As the model changes, and you add some old parts, they are migrated too, keeping your model up to date at all times.

[dan_butler_komatsu]

We could call this Migrate on Demand.

[wvos]

Think this would be a great time saving option.

[Anonymous]

Think it is a good idea.

[rainer.praeger]

We even go further with our thoughts. What about having an opportunity for an automated migration AND saving of write protected (i.e. released) In­ven­tor files!? Our users work with In­ven­tor 2024.3 & Vault Pro­fes­sio­nal 20­24.3 each day. Every time an assembly is opened, In­ven­tor automatically migrates the write protected files within too - so far so good. But: In many cases Vault on / before check in requires that all modified files have to be saved - even if they are write protected. And you have to do that save operation - otherwise check in is not possible. In large assemblies the save operation of all the many files the user really did not work on can take several minutes. Next day exactly the same will happen - even if the same user on the same computer has to work on the same assembly as yesterday. This costs us so much unnecessary time - again and again!

A technology to also save the automatically migrated write protected In­ven­tor files (especially IPTs and IAMs) - maybe in the background or maybe via Job-Ser­ver - would greatly reduce the time we have to spend today. Saving these files of course should only take place, if there was no error during migration. If errors occur during migration they should be logged, so that later one could work on or repair them manually. Migration errors - if they occur - should be logged, so that later one could work on or repair the respective files manually.

Another way would be having a Migration job directly within Vault.

Of course we do a migration of the In­ven­tor files residing in our Vault done by a CAD ad­mi­ni­stra­tor. But as we have alone 100000+ IPTs this is a real "long term programme". And even if we would reach the state of having all vaulted IPTs migrated, one has to keep in mind, that the same procedure has to be done again as soon as we have switched to next version of In­ven­tor. So think about this wish and offer a solution, please!

Thanks for reading!

[jens_dietzsch]

ok