Forum Discussion
Customer master table as a Dimension or Fact table?
Hi everyone,
I am working a data model with 4 fact tables - Sales (date level), Budget(month and product level), Salesman Route(date level), Orders (date level)- and 4 dimension tables - Customers, Products, Time, Warehouse.
The issue that I have is in Customers table, until this month we had only one row for each customer, from the next month we'll have one row for each customer for each date. It will have a new field (date_snapshot) in order to know what were the changes in the customers information, mainly the changes in Salesman_name to which customers belong. With this new field I'll have an ID_Address for each customer for each date.
The problem that we have with the new Customers table is the relationship with the fact tables, mainly with sales. Now the relationship is one-to-many but later it will be many-to-many and when we will have to know how many customers do we have, it will look like we have many customers (one for each date snapshot).
I really appreciate your help.
Rodriguez22 you will use DISTINCTCOUNT on customer id to get the unique list of customers instead of simple COUNT
✨ Follow us on LinkedIn and to our YouTube channel
I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make effort to give Kudos to whoever helped to solve your problem. It is a token of appreciation!
⚡ Visit us at https://perytus.com, your one-stop shop for Power BI-related projects/training/consultancy.
1 Reply
- parry2k
Super User
Rodriguez22 you will use DISTINCTCOUNT on customer id to get the unique list of customers instead of simple COUNT
✨ Follow us on LinkedIn and to our YouTube channel
I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make effort to give Kudos to whoever helped to solve your problem. It is a token of appreciation!
⚡ Visit us at https://perytus.com, your one-stop shop for Power BI-related projects/training/consultancy.