Forum Discussion

IvanS's avatar
IvanS
Icon for Helper V rankHelper 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.

amustafa's avatar
amustafa
Icon for Solution Sage rankSolution Sage
2 years ago

In your Customers dataset, make sure to have a unique row for each customer by let's say a Customer_ID and then you can have all other demograhic infomrmation about a customer in this table.

For Transactions table you can have a Customer_ID colun with all transaction details.

Join the two table on Customer_ID with 1 to many relationship.

Hope this helps.