Forum Discussion
SamyAbdul
Helper I
2 days agoSingle wide table and dimensional schema
Hi experts, I have asked similar question here, https://community.fabric.microsoft.com/discussions/ac_dataengineering/layered-approach-for-lh/5378549 But the requirements have become clear now, fo...
ShafiUllah-bc
Helper III
2 days agoHi SamyAbdul ,
Option 1 is right. On your specific question about observation periods and releases:
- Keep each Gold fact at its own grain and period. If one dataset is monthly and another is annual, make both periodic snapshot facts and link each to dim_date at its own level, for example the first day of the period. Do not force them into one snapshot.
- Treat source release as data, not as a filter. Store the release id on every fact row, plus an is_latest flag or a view that picks the latest release per hotel and period. Then reports default to current figures, and you can still reproduce older numbers.
- Combine across facts in the semantic model, not in a wide table. Both facts filter through dim_hotel and dim_date, and measures from each sit side by side in one visual. If one fact is coarser than dim_date, Power BI handles that with the higher grain fact pattern.
Docs:
https://learn.microsoft.com/en-us/fabric/data-warehouse/dimensional-modeling-fact-tables
https://learn.microsoft.com/en-us/power-bi/guidance/relationships-many-to-many
If this helps, please mark it as the solution.