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: You create measures that use the USERELATIONSHIP DAX function to filter sales on the inactive relationships between sales table and the date table.
Does this meet the goal?