Attached is a first shot at a unified datamodel based on feedback and experience in the field. Same tables have been worked out a bit more than others at this point in time, before fleshing them out further I decided to post it here to get your feedback in an early stage.
Valuelists: I think that the best is to have separate tables for each valuelist to keep the design nice and clean. Even though this implies at the moment a bit more work for the editing frontend.
Let me know what you think of it or if you need clarification on some of it’s parts.
Good to see that the UDM is starting to see the live-light. As promissed we will look at the UDM from a CRM perspective. I hope the following remarks will contribute to the finalization. If we have misinterpreted the UDM, I hope some clarification will follow.
At first glance, only basic fields have been added. This is not a problem per se, but for instace with respect to a company more fields will be neede for specific data.
The Order part looks rather basic. We will not focus on this for the momen. There is no distinction between Sales en Purchase.
The focus is clearly on the organisation. Organisations and contacts are placed in seperate tables. A contact can only be linked to 1 organisation, there is no combinationtabel.
Addresses are in seperate tables and are linked to organisations, not contacts.
The communications area is mainly focused on activities. True contact moment registration is missing, let alone e-mail and mailmerg.
I do miss some fields in the company-section:
I would like to add:
company_status
company_branche
company_region
company_priority
company_category
company_firstcontact
each with there own link to a seperate table.
also
company_manager (with a link to the user table!)
What do you exactly mean with the section: communications?
Because in the company-section I don’t see them, but in the contact-section, you allready have communications like: Phone_direct, phone_cell
I think in the order-items, you have to add the fields: productname, description etc..
and use alookup field to fill them. Because if you change something in the product category (like a price, or something) you don’t want to change this in older orders.
Also Price , unity, tax etc.. are missing.