Forum Discussion
Helper ICommon Date slicer for multiple visuals
Resolver IIII think the most common practice is to create a Date table that contains the dates that are in all of your tables. Usually, you want the Date table to start on January 1st of the oldest year in your data to December 31st of the highest year that you have in your tables. You do not want to have gaps in your Date table, I would use the CALENDAR function to create the Date table.
Once you have the Date table created, you can create a relationship between the Date table and CreatedDate, as well as, a relationship between the Date table and WarrantyDate. Once you have done this, you can use the Date table for your slicer and it will achieve your desired results.
prasavega - I tried creating the relationships as you mentioned but then I getting the following error: "You can't create active relationship between ServiceDeskSurvey and Calendar because that would introduce ambiguity between tables Calendar and Incidents. To make this relationship active, deactivate or delete one of the relationship between Calendar and Incidents first."
I am trying to apply same date slicer for tables- ServiceDeskSurvey (CreatedDate) and Incidents (CreatedDate). And there is no existing relationship between these two tables. However, I am getting the above mentioned error while creating relationship between the calendar - date column and the two tables date fields.
- vega
I believe that you are getting that error because you have a relationship between ServiceDeskSurvey and Incidents. You cannot have this relationship and then have a relationship between both and the date table. The reason is that there would be two different paths from Calendar and Incidents.
The first being Calendar -> Incidents
And the second being Calendar -> ServiceDeskSurvey -> Incidents
Power BI cannot handle this. There can only be one path to get from one table to another.