Get - Force Overwrite

[douthett]

Vault is currently set to not get the latest version of a file if that file already exist on your local and is newer than what is in Vault. 

This has hurt a number of our user who have told Vault to get the latest version of a file, not realizing their copy was newer than what was in Vault.  

We would like to have the option to set ‘Working Folder – Force Overwrite’ as default.  This would insure that we have the latest version every time.  And with the warning that I’m going to Overwrite the files, I can stop the process if I realize that I don’t’ want to overwrite the files

[tschaeferZNBXX]

I wish I could vote this up a million times!

This has burnt us many times and multiple people making the same changes or updating parts based off of an older version that is in their workspace.

[Anonymous]

As an option to default, 100% yes please.

[mschindler-mum]

The function was very useful, until it is replaced with the manual "workflow" trough force overwrite in the get dialog.

Hopefully, we get the function back in the new version and in Dot.Updates.

Many thanks, for confusing us, and customers.

Regards,

Matthias Schindler
CAD/CAM/PDM technical specialist at

[mschindler-mum]

Hi Vault development and Vault productmanagement team,

• Why does this idea in this status already.
• How many votes does it need to go to the next status, or go on the roadmap?
• Is it planed for one of the next releases, or an dot update?

Any reply would be nice @YounesYammouri.

Many thanks,

Kind regards,

Matthias Schindler
CAD/CAM/PDM technical specialist at

[YounesYammouri]

@mschindler-mum 

Hi Matthias,

Yes this is something part of the product roadmap and will be addressed in one of the next releases.

Best regards

Younes

[mschindler-mum]

Hi @YounesYammouri,

That sounds good. 🙂

Kind regards,

Matthias Schindler
CAD/CAM/PDM technical specialist at

[Silvia.van.Emmerik]

As a basic rule I think that when a file is not checked out the PDM-system always contains the truth.

(despite whatever users tend to do on their local workspace)

However Vault focusses too much on local files, this can result in dangerous situations.

Suppose you have a file which is locally changed:

There are several options to see  the document:

• View:                   gives the version stored in Vault
• Open:                  gives you the local version
• Check out:           gives the local version
• Get:                      gives the local version
• Get\overwrite:   gives the version stored in Vault
• Synchronise Workspace: keeps the local version (why)

If a user wants to checkout this file and doesn't pay close attention, Vault will in most cases use the local copy, which is not what the user expects. The only warning now is this green dot (with green being the worst choice of color)

My advice to our users now is to always do a get\overwrite.

Personally I'd like to have the option overwrite as a default, but at least I'd like a warning saying something like:

"your local copy differs from the Vault version, do you want to overwrite the local version?" (default: Yes)

[Senthil_Kumar]

Hi,

Can you please review this Idea - https://forums.autodesk.com/t5/vault-ideas/get-force-overwrite/idi-p/6968826 ? This one we are looking into. Will this solve your issue?

[Silvia.van.Emmerik]

Yes, Thank you, that's exactly the issue. Really hope this will be implemented soon.

[Senthil_Kumar]

We have implemented this in Vault 2020.1 Update.

[MarkusGreifeneder3360]

Hi,

I was very happy reading about adding this setting.

Unfortunately, it does not function for children of an assembly.

Opening an assembly from vault in inventor using a double-click, and parts of this assembly are newer on the local disc, these parts will not be overritten with the vault content.

Of course it works with a get and adding the children to;

but the engineers open assemblies with double-click.

This issue causes problems, with some of our users.

Is it possible to add this optional function too?

[Hunteil]

Could someone link us to the implemented feature please? I would like to know how it was implemented for future use when my team updates all the software (maybe a video explaining how it works and how to activate/deactivate it). That and I want to know just in case it was activated automatically without us knowing.

[Senthil_Kumar]

Hi,

Everything that is changed is documented in the help page - https://help.autodesk.com/view/VAULT/2022/ENU/?guid=GUID-91636F7C-2FA9-4141-9462-66227AD966FB

Hope this helps.

[gkniksch_aep]

@MarkusGreifeneder3360, I just added an idea to the idea board for the double-click behavior you're looking for. Users in my organization are interested in this as well. Cheers.

Alter Double-Click file behavior to follow 'Get' Settings - Autodesk Community