Read Only

Hello,

In the latest version of M-Files (21.x) a lot of new settings appeared in Advanced Vault Settings in Configuration.

You can set to always update the Metadata in files in Client -> Desktop -> Files Operations -> Promp for Updating Properties -> Update Always

Dear Radu Moca

Many thanks for the response. I am using M-Files 20.10.9524.7 and the Client setting is not there. Is there any other way to set this up. Also if I need to upgrade, is it just a wizard setup or are there any custom configurations. I prefer not to update as many users are using the application.

Thank you

1) There might be a registry setting that need to be applied to every workstation

2) There might be an option to add this settings to all workstations via Custom Vault Data

3) There is an API Method to Update Metadata in File, so you need to run a script, maybe in an event handler, Before CheckIn Changes to do the update.

For 1 and 2, this is not documented opinion. It might be also one registry setting at server level.

For 3) M-Files API - UpdateMetadataInFile Method (m-files.com)

Dear Radu Moca

This looks very complicated. Any idea how can I upgrade M-Files. Is it any easy update. I have 3 vaults running on SQL server

I would suggest that you work with your local reseller.  Whilst the upgrade itself is typically fairly straight-forward, you would need to ensure that you have backups and the like in place to ensure that you have a rollback strategy in case of something unexpected happening.

Thank you, since we have created the vaults using company resources and not the local reseller they are not going to update the M-Files. Is there a roll back document just in case.

Hi YST,

This is going far off topic of the original post...

My suggestion would be to have a full backup of the entire environment before any upgrade, if you can.  There are a variety of documents in our Knowledgebase about how you should have your environment configured for backups.  I would read all of these, put in place the various processes and procedures, test them, then look at how to move forward with an upgrade*.

• M-Files Backup Policy.pdf
• Maintenance Guidelines for M-Files Administrators.pdf
• Best Practices for Data Security and High Availability in M-Files.pdf
• Using Microsoft SQL Server as the Database Engine (m-files.com)
• M-Files Best Practices - Applying Controlled Changes to an M-Files System.pdf

There are some other documents around best practice (e.g. encryption, always-on availability groups, etc.), but I think the above are the primary ones for backup and continuity.

Regards,

Craig.

* Note: I am not trying to be alarmist here, but I am concerned that without referring to the above documentation - at least - you may well have a system which is not able to recover in case of something unexpected happening, such as a disk failure, data corruption, or OS issue.

Hi YST,

This is going far off topic of the original post...

My suggestion would be to have a full backup of the entire environment before any upgrade, if you can.  There are a variety of documents in our Knowledgebase about how you should have your environment configured for backups.  I would read all of these, put in place the various processes and procedures, test them, then look at how to move forward with an upgrade*.

• M-Files Backup Policy.pdf
• Maintenance Guidelines for M-Files Administrators.pdf
• Best Practices for Data Security and High Availability in M-Files.pdf
• Using Microsoft SQL Server as the Database Engine (m-files.com)
• M-Files Best Practices - Applying Controlled Changes to an M-Files System.pdf

There are some other documents around best practice (e.g. encryption, always-on availability groups, etc.), but I think the above are the primary ones for backup and continuity.

Regards,

Craig.

* Note: I am not trying to be alarmist here, but I am concerned that without referring to the above documentation - at least - you may well have a system which is not able to recover in case of something unexpected happening, such as a disk failure, data corruption, or OS issue.