Forum Discussion
Third table relationship
- 3 years ago
Here is my guess to your problem. You may have an existing relationship between table1 and table2. When you are trying to create an active relationship between your month dimension and table2, you get an ambiguity error. There would be two possible paths for the engine to get to table2.
Have you thought about this design?
It will allow you to filter and group by these dimensions:
Not direct, but I think there is some indirect relation with the field "Product", as they both are linked to the table with product details.
I think that is the problem, but I cannot break that relationship..
Hi,
Just as you created a Month dimension table, you should also create a Product dimension table. Remove any relationships between Table1 and Table2.
- HitcH3 years agoHelper II
Thank you Ashis!
One additional question, now I could handle it, but I still have some problem on the Month relationship:You can see the two tables connected to each other via the "match" table in the middle. Still if I create a table with YearMonth1 and YearMonth2 together I get an error (while I can create YearMonth1 with YearMonthMatch or YearMonth2 with YearMonthMatch singularily). What am I still missing? 😞
Thanks again!
- Ashish_Mathur3 years agoSuper User
Hi,
In each of the Fact tables you should create a Date column from the Yearmonth column. Create a Calendar Table. Build a relationship from the Date column of hte 2 Fact Tables to the Date column of the Calendar Table. In the Calendar Table, create columns of Year, Month name and Month number. Sort the Month name column by the Month number column. To any visual/slicer, drag any Date related column from the Calendar Table.