Composite Model - Calculated column in import table that sums data from related direct query table

Hi Av1ator ,

Based on the information you have provided, it is possible to efficiently create and use calculated columns in a composite model. However, there are specific limitations when these calculations span different source groups, such as between DirectQuery and imported data. The errors you encounter are usually due to these limitations.

In a composite model, although you can create relationships between tables in the DirectQuery source and imported data, it can be challenging to attempt calculations that aggregate or summarise data from these source types because the DirectQuery source handles and stores data differently from imported data.

Creating measures is the recommended method for aggregating data from different source groups in a composite model. Measures are dynamically calculated at query time, allowing for aggregation to be handled across DirectQuery and imported data. If possible, consider specifying calculations either directly in the source system of the DirectQuery table or during the data import process of the importing table. This way, the calculation becomes part of the data model without crossing source group boundaries.

For more information about composite models and their limitations, we recommend that you read the following documentation:

Use composite models in Power BI Desktop - Power BI | Microsoft Learn

Composite model guidance in Power BI Desktop - Power BI | Microsoft Learn

Best Regards,

Ada Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.