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 399 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
  • I have just spent the last couple of months to prototype and build our metadata structure. The key to me was to build something, and then to test it by filing some test documents to establish if I have the appropriate level of properties, value lists, classes etc. It became very complex which then lead me to a phase of optimising it; simplifying it; reducing the number of document types, making more use of templates etc. It is also important to relate each metadata design compotent with the views and how the users will ultimately want to use the metadata to manage their desk and the business.

    it was a real journey (and not yet completely done). What I do know is the more time I use in the design phase the less time I will have to spend ultimately to find quick solutions for problems that I did not foresee.
Reply
  • I have just spent the last couple of months to prototype and build our metadata structure. The key to me was to build something, and then to test it by filing some test documents to establish if I have the appropriate level of properties, value lists, classes etc. It became very complex which then lead me to a phase of optimising it; simplifying it; reducing the number of document types, making more use of templates etc. It is also important to relate each metadata design compotent with the views and how the users will ultimately want to use the metadata to manage their desk and the business.

    it was a real journey (and not yet completely done). What I do know is the more time I use in the design phase the less time I will have to spend ultimately to find quick solutions for problems that I did not foresee.
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.