How do I Change the Naming Convention of Multifiles?

Hello,

Multifiles on our system force the first file added to them to adopt the same name, and I would like to change this behaviour.  

For example, let's say we have an empty multifile titled "Customer Questions".  I would like to add the file called "Question 1" to this multifile.  When I do this, the file "Question 1" is renamed to "Customer Questions"; the same name as the multifile itself.  Then, if I want to add another file "Question 2" to this multifile (which already contains 1 file), that next file will keep its name.  So I now have a multifile titled "Customer Questions", with two files: "Customer Questions" and "Question 2".

I do not believe that this is the default behaviour of multifiles, and I assume that this behaviour is controlled somewhere in M-Files Admin, though I'm at a loss as to where.  I do not want the multifiles to change the names of files that get added to them.

Where and how can I change this behaviour? 

Thank you

  • Hello,

    Maybe you can use Document Collections, and not Multi Files Documents.

  • Thanks for the suggestion, but for the way we are working, we must use multifiles.

  • To my understanding, any file that is added to the MFD automatically assumes the metadata card of that MFD.

    When I have used this functionality, I have been able to create a MFD first, then drag and drop the documents, and they have retained their original File name title in M-Files, however the metadata card is the same as the MFD metadata card. In my case this is not a problem. Let me know if you want to see my set up and how it looks, I am happy to collaborate and learn more.

    What is the end point that you need? If it is a specific view, then perhaps you can use a property field with a value list. or keywords? 

  • Thanks for taking the time to write this out.  I agree with what you say about multifiles: all documents within share the same metadata except that they can all have their own names.  

    When I create a multifile and then drag-and-drop files onto it, I get this problem that the first file is auto-renamed to the name of the multifile.  All files after this first file keep their names.  I should also mention that if I try to change the name of the first added file, it reverts back to the name of the multifile.  

    Now!  If I create a multifile through the MFilesAPI and add source files to it, I do not get this problem.  Somehow creating them programmatically allows me to bypass this rule.

    My real question is this: I am pretty certain that this behaviour is controlled somewhere in the M-Files Admin tool, but I have done some looking around and I cannot find anything.  Where in M-Files Admin tool is the default behaviour of multifiles controlled?  

  • Are you talking about the file name or the Property 'Name or title'?

    Every documentadded to the MFD will have the same metadata which means that they will all have the same value for 'Name or title' and that cannot be changed without changing it for all.

    However every documentcan still have a seperate file name. You can change that file name after it's been added by right clicking on the document and selecting 'Rename'

    There is not currently a way to change this behavior that I know of.

  • Thanks for the suggestion.  To answer you first, I must be talking about the file name.  Trying your method to change the fiel name doesn't fix the problem.  I've attached pictures below to show more:

    Here is a multifile with the name "Test", and one file inside of it named "Test".

    Here I enter a new name for the file, and hit Enter:

    And the name reverts back to the multifile's name:

    Again, this only occurs for the first file.  See below how I have added the file "Any name is fine" to this same multifile and it keeps its name:

  • I'm not sure what's going on there, but in general the files should be able to have whatever name you want; they aren't tied to the MFD's name.  Here's an example of me renaming a file:

    I can envisage two options here:

    1. Some code within your system is causing the rename to fail.  Do you have anything installed that might cause this?  If you have a partner that helped install/configure the system it may be worth checking with them whether anything was installed that could cause this.
    2. There's some bug that is causing this.

    If you have a partner then I'd look to work with them.  If not then I would probably raise this as a support ticket (support@m-files.com), as I don't believe that this is expected behaviour.

    Regards,

    Craig.

  • Hi Craig,

    That makes good sense to me.  I'll do another thorough check through our codes, and if that doesn't turn anything up, support it is!

    Thanks