Forum Discussion
Super UserManage aggregations multiple fact tables DirectLake over OneLake
Hello Jacek,
In aggregatinos tables, the user cannot force which table is used. If they select “Month” in a slicer, the engine may still query the daily table if the visual structure doesn’t match the aggregation definition.
Aggregations are designed for performance optimization, not user-driven logic. But in calculation groups there is explicit user control, the slicer dictates exactly which table is queried.
Best,
Anıl
Super UserHello jaryszek ,
You can create a composite model with calculation groups. For this, you need Tabular Editor (or another TOM/ALM-based tool) to add a calculation group into your model.
After that you can create a disconnected parameter table:
Granularity = DATATABLE(
"Level", STRING,
{
{"Daily"},
{"Monthly"}
}
)
And then you should define a calculation group like "Granularity Selection" with a calculation item like:
Selected Value =
SWITCH(
SELECTEDVALUE(Granularity[Level]),
"Daily", CALCULATE(SUM(fct_table_daily[Amount])),
"Monthly", CALCULATE(SUM(fct_table_monthly[Amount]))
)
If this solved your issue, please mark it as the accepted solution. ✅
Super UserHello,
why this is better than Aggregations tables?
Best,
Jacek
- anilelmastasi
Hello Jacek,
In aggregatinos tables, the user cannot force which table is used. If they select “Month” in a slicer, the engine may still query the daily table if the visual structure doesn’t match the aggregation definition.
Aggregations are designed for performance optimization, not user-driven logic. But in calculation groups there is explicit user control, the slicer dictates exactly which table is queried.
Best,
Anıl
- jaryszek
thank you.
This is great answer!- anilelmastasi
You are welcome Jacek, could you please accept as solution 🙂