Keeping file names intact

Here's a quick partial answer to your question:

I'm afraid there's nothing much you can do to avoid these IDs in document names. M-Files
need the IDs to uniquely address each object in the vault. And in usual M-Files environments it's not only about the file names, but also about the views, vault connections and such. And sometimes it is important to make sure that a document can be linked to from different operating environments.

Since M-Files users may have document vault connections with different names, and each user may have different views, M-Files provides a function to create a universal shortcut to a document. The operation of the shortcut is not affected by the above factors.

Such links might be used in, e.g., e-mail messages in which you refer to the organization's documents, or in your program code or similar. To do this, use the "Create or get shortcut" from the document's pop-up menu. You will get something like this:

m-files://show/890FC3B2-7CFA-4959-B884-8A4D8D70EEFC/0-5

Where the "890FC3B2-7CFA-4959-B884-8A4D8D70EEFC" is the vault GUID, 0 is the object type ID and 5 is the object ID.

I'm sure that people from Motive Systems will be able to shed even more light on this, if they have time. There are some nice tricks how M-Files overcomes a lot of these kind of situations automatically, where a document or a file refers to other one in the same vault.

Now what would be the best solution in your case? Would it be possible that all of the project team would use M-Files, so you wouldn't have to send these projects and presentation by email? It could also save a lot of network traffic. How about just sending an M-Files link in the email?

Best regards,
Samppa

If you are importing a lot of documents that have dependencies, one thing to try is "Paste as Multi-File Document." Multi-File documents have a lot of drawbacks, but are very quick and easy to create and in a lot of cases dependencies will still work in them (since M-Files stores them as real folders).