Calculated tables are not being refreshed automatically anymore

[Koraomy]

Calculated tables are not being refreshed automatically anymore even with dataset refresh, need a manual change in the DAX before they change. This is a new issue for me, usually they get updated without any intervention. 

The storage mode is Mixed

[v-pgoloju]

Hi @Koraomy,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @divyed and @tayloramy  for prompt and helpful responses.

Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[divyed]

Hello @Koraomy ,

It was working previuosly so I assume your calcluated tables are based on tables with import mode. you can check dew more things here :

1. Check the DAX for the calculated table. If it references a DQ table, the calculated table might only be updated when the DAX formula is changed or when the Imported tables it uses are refreshed. Ensure all dependent Imported tables are successfully refreshing. If it is only based on DQ data, a standard dataset refresh might not be enough unless the underlying DQ source schema or data changes are explicitly detected by Power BI.

2. Check if your DAX query is not static, means it should not reference only tables/columns that do no change

3. You can try adding something like reference to last refresh date to check if this is working fine.

I hope this helps.

Did I answer your query ? Mark this as solution if this helps, Kudos are apprecaited.

Cheers.

[Koraomy]

Thanks divyed!

Can you please elaborate on this?

"Standard dataset refresh might not be enough unless the underlying DQ source schema or data changes are explicitly detected by Power BI."

My table only uses DQ data, and let's assume the schema didn't change. What do you mean by "data changes are explicitly detected by Power BI."

[divyed]

Hello @Koraomy 

I meant schema changes require a Power BI Desktop refresh and visual updates are not always consistant .Different visuals or internal queries in one visual can execute at slightly different times.

You can create a view at source and use it in your model, this will give you updated data always. 

I hope this helps.

Cheers

[tayloramy · Accepted solution]

Hi @Koraomy,

Calculated tables are always Import-mode objects. They only recompute during a model refresh and don’t automatically update off DirectQuery tables in a Mixed/Composite model. In fact, when a calculated table references a DirectQuery table, Power BI won’t recalc it from that DQ source; visuals over the DQ table will show the latest data, but visuals over the calculated table will stay at whatever the calculated table had at its last successful refresh - until you manually edit the DAX (which forces a recalc) or do a refresh that actually touches its dependencies. See Microsoft’s docs on calculated tables and composite models for the fine print: Create calculated tables and Composite models.

Quick solution

1. If your calculated table depends on any DirectQuery (or Dual) table, move that logic out of the calculated table:
   • Rebuild it in Power Query (M) so it runs at refresh time, or
   • Materialize the needed data into an Import table (e.g., via a Dataflow/Lakehouse/Warehouse), then point the calculated table to that Import source.
2. Double-check the table’s “Include in report refresh” property is ON (Model view > select table > Properties). If it’s OFF, the table will never recalc during refresh. Reference: Data refresh overview.
3. If you need “latest” values without waiting for a model refresh, don’t use a calculated table - use measures over the DirectQuery tables instead.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[Koraomy]

Thanks for the comprehensive reply.

I see I should have included a bit more informaiton. 

The calculated table is based on only DirectQuery data, and for months when you open the report that table gets updates with the newest data.

This time, only changing DAX triggered a refresh for the table. "Refresh" button changes nothing.

From the documentation:

Calculated tables are always imported, and their data is refreshed when you refresh the tables. If a calculated table refers to a DirectQuery table, visuals that refer to the DirectQuery table always show the latest values in the underlying source. Alternatively, visuals that refer to the calculated table show the values at the time when the calculated table was last refreshed.

In the case with DirectQuery, the table will only reflect the changes after the semantic model is refreshed. If a table needs to use DirectQuery, it's best to have the calculated table in DirectQuery as well.

It's not clear when the calculated table based on DirectQuery are "last refreshed" still at least on paper it should have refreshed when the Semantic Model, so maybe this is the first month the model didn't change, just the data if I understand it correctly. It also looks like this is not a recommended use for the claculated tables.

I agree that rebuilding it in via Power Query (M) will solve this, if nothing has changed to the desktop reports that can be fixed.