Forum Discussion
Data Model Design Question - Redundant Date Tables
I think the model needs reconsideration. For example, if you need a ticket as both fact and Dim, then you should have two copies one a DIm and one as fact
So the model will be LikeDate - dim
Ticket - Dim
Ticket - Fact
Pipeline -> Activity ->Hits -> combine Fact
If need have Pipeline and Activity as Dim
Join Date with Ticket Fact , Combined fact
Ticket with Ticket and combined fact
In this model, you can have an independent table if needed. Attached file - Without join date table for Active, Created, and Resolved (Use same logic as HR). Second with the Joined date table, the same stuff
Power BI: HR Analytics - Employees as on Date : https://youtu.be/e6Y-l_JtCq4
https://community.powerbi.com/t5/Community-Blog/HR-Analytics-Active-Employee-Hire-and-Termination-trend/ba-p/882970
Power BI HR Active Employee Tenure Bucketing, and Hired, Terminated, and Active employees: https://youtu.be/fvgcx8QLqZU
I think the model needs reconsideration. For example, if you need a ticket as both fact and Dim, then you should have two copies one a DIm and one as fact
So the model will be Like
Date - dim
Ticket - Dim
Ticket - Fact
Pipeline -> Activity ->Hits -> combine Fact
If need have Pipeline and Activity as Dim
Join Date with Ticket Fact , Combined fact
Ticket with Ticket and combined fact
In this model, you can have an independent table if needed. Attached file - Without join date table for Active, Created, and Resolved (Use same logic as HR). Second with the Joined date table, the same stuff
Power BI: HR Analytics - Employees as on Date : https://youtu.be/e6Y-l_JtCq4
https://community.powerbi.com/t5/Community-Blog/HR-Analytics-Active-Employee-Hire-and-Termination-trend/ba-p/882970
Power BI HR Active Employee Tenure Bucketing, and Hired, Terminated, and Active employees: https://youtu.be/fvgcx8QLqZU