Do you have a general Contact Detail table?
  v4.0 Posted at 25/09/2020 3:47 AM by Tiago Araujo

It is common to have a Contact Detail table to store your contact information such as phone numbers. Below is an example of a Contact Detail table and its related tables. This is bad because the PartyPhone table is too specific for a phone number and you have to add a new table to save an email or other contact information if this is needed in the future.​

Figure: Bad Example - A too specific Contact Detail table

We normally have a general Contact Detail table that includes all the different categories of phone numbers, whether it is shared or primary plus emails all in the same table.

Figure: Good Example - A general Contact Detail table

We use a Contact Detail Category table to store these categories.

Figure: Good Example - Details of Contact Detail Category table

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address: