Forum Discussion

IvanS's avatar
IvanS
Helper V
2 years ago
Solved

How to avoid ambiguity between 2 DIM and 1 FACT table

Hi guys,   I have created simplified schema of my dataset below. I would like to visualize:   1. Transactions per date 2. Customers per registration date   With current set up, I am unable to ...
Need Help
Tips and Tricks
  • CoreyP's avatar
    CoreyP
    2 years ago

    Yeah, for sure. However, as you're wanting to aggregate customers by registration date.. that technically means it should be considered a fact table in a star schema. 

     

    So, you are correct in your OP. Your two options are to restructure your model, or add USERELATIONSHIP to your measures.

IvanS's avatar
IvanS
Helper V
2 years ago

Hi CoreyP ,

the Customer table is dimensional as Customer ID is unique there and there is only one registered date assigned to unique Customer ID - example:

Customer IDNameLanguageRegistration dateCityCountry
1Johnnyen1.1.2024New YorkUS
2Simonfr20.12.2023ParisFrance

 

So creating distinct list of customer ID's will lead into having duplicate table of the same size (which is actually that I am doing right now) but I am looking for ways to reduce size of dataset.

CoreyP's avatar
CoreyP
Solution Sage
2 years ago

Yeah, for sure. However, as you're wanting to aggregate customers by registration date.. that technically means it should be considered a fact table in a star schema. 

 

So, you are correct in your OP. Your two options are to restructure your model, or add USERELATIONSHIP to your measures.