5/27/2023 0 Comments Filemaker pro database examples![]() For one, we duplicate the effort of creating and maintaining the fields. But it's less than ideal to store the same data in two places within a database. The temptation here would be to include a phone number field in both the Contacts module AND the Company module. We need to be able to differentiate and easily find the company phone number as opposed to the contact's phone number. What’s unusual here is that both the Companies and Contacts modules will need their own unique place to hold that information. Now one piece of information we haven’t accounted for is the actual contact information – like phone, address, email, etc. What does that look like? In an ERD, we indicate the nature of the relationship using a specific kind of line notation connecting the entities. Interactions are usually associated with an actual person, so we would only link interactions to contacts. A company can have multiple contacts, but generally, contacts only have one company. ![]() Next, let's think about how they would be linked. ![]() L et’s start with our main three modules: Contacts, Companies, and Interactions. Normalizing means we will look for instances where we can avoid entering the same data in two different areas. As part of this process, we will look for places to normalize the data. In database land, this is a map of all the buckets of information that we will track and the connected data among them. Next, we need to draw up an entity relationship diagram - ERD for short. Yet, we’re not quite ready to start writing code. In our previous blog post, we reviewed what a customer relationship management (CRM) system is and put together the requirements for a basic CRM.
0 Comments
Leave a Reply. |