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
    Sorry, no answer to your question how you can restore a sample vault.
    I have a follow up question based on the thread above.

    Jason refers to "use document templates instead of creating classes. Originally, I used classes to determine what properties to show to users. I thought it would be easier for them - but the multitude of classes just ended up being confusing. Templates would have accomplished the same thing, and would have also provided a consistent format for many document types."
    However, if you use a template that still needs to be saved to a class right? So I am not sure how templates overcome creating multiple classes.
    We have 'document types' under a particular class, to reduce the number of classes. (See screenshot).
Reply
  • Former Member
    Former Member
    Sorry, no answer to your question how you can restore a sample vault.
    I have a follow up question based on the thread above.

    Jason refers to "use document templates instead of creating classes. Originally, I used classes to determine what properties to show to users. I thought it would be easier for them - but the multitude of classes just ended up being confusing. Templates would have accomplished the same thing, and would have also provided a consistent format for many document types."
    However, if you use a template that still needs to be saved to a class right? So I am not sure how templates overcome creating multiple classes.
    We have 'document types' under a particular class, to reduce the number of classes. (See screenshot).
Children
No Data