What's wrong the date or it's my data model?

[selected_]

I have a 3 tables with dates in each tables so I created a table just for DATE with this DAX code

DimDate_DAX = ADDCOLUMNS ( CALENDAR("2017-01-01",TODAY()), "Year", Year([Date]), "Quarter", CONCATENATE("Q",ROUNDUP(MONTH([Date])/3,0)), "Month", MONTH([Date]), "MonthName", FORMAT([Date],"MMMM"), "WeekNumber", WEEKNUM([Date]), "WeekDay",WEEKDAY([Date]), "Day", DAY([Date]), "DayName", FORMAT([Date],"DDDD") )

And then I created relationship between those date columns in other 3 tables to the new DATE table I just created, but in some visual and in some year it shows blank for some visual, but with own date table it works well.

I don't know if its the relashionship that are wrong, the Cardinality are set on Many to one and cross filter by Single. I have tried to change the Cardinality to One to Many but it says not vaild for this relationship

[MattAllington]

Best practice is to create a calendar table containing all dates from the start of the year of the first date in all fact tables to the end of the year of the last date in all fact tables. Personally I never create date tables in DAX. You can copy my power query table from here 

https://exceleratorbi.com.au/build-reusable-calendar-table-power-query/

and read about calendar tables here https://exceleratorbi.com.au/power-pivot-calendar-tables/

[selected_]

@MattAllington 

I tried your method but it still same issue.

[selected_]

I solved.

Issue was that the Date in the other table had also time inside so I removed the time and remain only day and year. 

[AllisonKennedy · Accepted solution]

@selected_
What does your date look like in the orignal tables? It needs to match the date table EXACTLY. I typically use a DateKey in the format YYYYMMDD so that there is no ambiguous dates that don't match, especially if you are using date/time this can be important.