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
  • Simon's comments are good advice. Keep it simple from the start. You can always add more details, but it can be difficult to remove them once you have started using them. So if there is no good reason, then don't create more properties or classes. Even if there seems to be a good reason, then consider the extra work required from the user. Will they accept it or will they stop using the system or find a way around it? If so, you have not gained anything but may have lost your chance to make it a successful implementation. As Simon mentioned the quantities involved makes a big difference. Extra time spent on rare occasions is acceptable, but for those documents that come in piles every day, you really need to make it simple and quick to work with.
    Karl
Reply
  • Simon's comments are good advice. Keep it simple from the start. You can always add more details, but it can be difficult to remove them once you have started using them. So if there is no good reason, then don't create more properties or classes. Even if there seems to be a good reason, then consider the extra work required from the user. Will they accept it or will they stop using the system or find a way around it? If so, you have not gained anything but may have lost your chance to make it a successful implementation. As Simon mentioned the quantities involved makes a big difference. Extra time spent on rare occasions is acceptable, but for those documents that come in piles every day, you really need to make it simple and quick to work with.
    Karl
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.