M-Files is a 2025 Gartner Peer Insights Customers' Choice for Document Management
️️➡️Download the report!

Options
  • Locked Locked
  • Replies 18 replies
  • Subscribers 9 subscribers
  • Views 411 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Comprehensive manuals or other help to set up Metadata Structure

Former Member
Former Member
Though I always thought that I'm not stupid I have really hard time setting up (rather complex) Metadata Structure.
User guide that I got from M-Files is next to nothing. Unfortunately the help is not better - actually I've never seen worse. M-files offer something (that I doubt would be what I truly need) for "modest" fee of EUR 500+?
Does anybody have advice how to set up Metadata Structure this on budget that does not break my bank account?
What I truly need is the 'best practices' how to use Object Types, in conjunction with Value Lists and Property Definitions in order to get proper Contact type/Contact/Contact Person/Project/Document relationships. So when I select specific Contact type (Client, Prospect, Vendor, ...) only appropriate list of companies appears in Contact property dropdown, and only appropriate list of project names appears in Project property dropdown, and so on. Also how to use Value lists and Sublists - when is appropriate to import values from db, and when enter manually via M-Files client.
Parents
  • Former Member
    Former Member
    Just to clarify - you are correct, you do have to create classes. But let's say for example that you have to store several types of non-disclosure agreements (NDA). Each type has some properties in common, but also you want to include some properties that are specific to each type. Rather than creating multiple NDA classes (e.g. "Customer NDA", "Supplier NDA", etc.), you might instead create one "NDA" class and just use document templates for each type. If you give each template the correct properties when you save it, you'll accomplish the same thing with an easier-to-understand vault structure for your users.

    Jason
Reply
  • Former Member
    Former Member
    Just to clarify - you are correct, you do have to create classes. But let's say for example that you have to store several types of non-disclosure agreements (NDA). Each type has some properties in common, but also you want to include some properties that are specific to each type. Rather than creating multiple NDA classes (e.g. "Customer NDA", "Supplier NDA", etc.), you might instead create one "NDA" class and just use document templates for each type. If you give each template the correct properties when you save it, you'll accomplish the same thing with an easier-to-understand vault structure for your users.

    Jason
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.