How do I Change the Naming Convention of 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?  

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?