Date relationship problem

[o59393]

hi all

I have 2 tables, both contain a day by dat date column in yyyy-mm-dd format.

There is a code asociated with each of the days. Code SP/B-0144.11 starts on 2/15/2019, while SP/B-0171.00 goes from 1/1/2017 to 2/14/2019.

When I create a table I see the following:

The year filter has effect on the left table however is duplicating the code per day. When it should only show once per day.

On the right table the code is showing correctly per date, however the year filter is not having effect.

My relationship looks like this

The bridge is done by merge columns, both consist of the combonation of country+product name.

I tried doing a 3rd table which is a calendar and I tried to link it to both existig tables but i got one inactive relationship

Here is the pbix

The expected solution is to get both tables work with the year filter, and have one day only per row (no duplicates) showing the respective code, where the transition of code would be 2/15/2019.

Any idea how to get it ok?

[Greg_Deckler · Accepted solution]

Get rid of the many-to-many, they are evil, make things not work properly and are almost always avoidable. Implement a bridge table of unique key values.

[o59393]

Hi @Greg_Deckler 

The problem is that products are added on a daily basis. Maintain a key of product+country will be kinda difficult.

Any suggestion?

[Greg_Deckler]

Bridge Table = 

  DISTINCT(

    UNION(

      SELECTCOLUMNS('Query1',"Merged",[Merged]),

      SELECTCOLUMNS('Formulas',"Merged",[Merged])

    )

  )

Zero maintenance required.

[o59393]

hi @Greg_Deckler 

Here it is:

But the values are still not filtering correctly:

thanks!

[Greg_Deckler]

Try making the relationships Both direction

[o59393]

it's not showing left table and right table will not show only 2019.

Thanks again!

[Greg_Deckler]

OK, let's back up, what are we trying to do here overall?  Take a look at what I did with your date table (Table) and the Model. Use your dimension tables like your calendar table and bridge table to affect both of your fact tables.

Attached below.

[o59393]

hi @Greg_Deckler 

I realized that my relationship model is not so good, and you confirmed me that by avoiding  many to many relationships. In fact im havind some issues creating dax, so I need to get this relations set properly. 

I checked your solution and found out that for example when i select a brand, the code wont filter at all:

For example for CR I have the following codes for that brand: 

I did a table with the code + column date of formula and another table  with code + date of query1 and didnt work well:

https://1drv.ms/u/s!ApgeWwGTKtFdhks4LrGKQB-RfqCQ?e=tQFLfi

Appreciate your help!