Forum Discussion
Multiple Relationships on Direct Query Feed
Hi JohnnyT48 ,
Relationships based on multiple columns should be avoided in the table model, even in DirectQuery. Relationships based on a single native column always generate better query plans in DirectQuery. When native columns are not available, you should use COMBINEVALUES to create calculated columns in both tables to define the relationship between them. More details can be found at the link: Using COMBINEVALUES to optimize DirectQuery performance - SQLBI.
More detailed information about the direct query model can be found in the documentation:
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
DirectQuery in Power BI - Power BI | Microsoft LearnIf your Current Period does not refer to this, please clarify in a follow-up reply.
Best Regards,
Clara Gong
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi JohnnyT48 ,
Relationships based on multiple columns should be avoided in the table model, even in DirectQuery. Relationships based on a single native column always generate better query plans in DirectQuery. When native columns are not available, you should use COMBINEVALUES to create calculated columns in both tables to define the relationship between them. More details can be found at the link: Using COMBINEVALUES to optimize DirectQuery performance - SQLBI.
More detailed information about the direct query model can be found in the documentation:
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
DirectQuery in Power BI - Power BI | Microsoft Learn
If your Current Period does not refer to this, please clarify in a follow-up reply.
Best Regards,
Clara Gong
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.