MENU
Adding an index key and normalizing casing in the data source would help resolve issues with undefined values and errors in a case-sensitive column. The index key can provide a unique identifier, and normalizing casing ensures consistency in the data, which would likely prevent the errors you encountered in the Power BI semantic model.
You have a Power BI data model that imports a date table and a sales table from an Azure SQL database data source. The sales table has the following date foreign keys.
* Due Date
* Order Date
* Delivery Date
You need to support the analysis of sales over time based on all three dates at the same time.
Solution: For each date foreign key, you add inactive relationships between the sales table and the date table.
Does this meet the goal?
Simply adding inactive relationships between the sales table and the date table for each date foreign key does not fully meet the goal. While inactive relationships allow for flexibility, they alone do not enable analysis over time based on all three dates simultaneously.
To achieve this, you would need to use DAX functions like USERELATIONSHIP to activate the appropriate relationship in your measures. Without this, the inactive relationships won't be utilized in your calculations, meaning that analysis based on those dates won't work as intended.