Forum Discussion
Refresh All and Service refresh not returning new data — manual table refresh works fine
Hi chelly911,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to garvitgupta96, Lodha_Jaydeep, for those inputs on this thread.
The issue is not with the gateway or data load, but with semantic model processing failures. Your refresh is successfully pulling data (as seen from the row count), but the warnings like missing columns/tables, invalid DAX, and type mismatches indicate that parts of the model (calculated columns, measures, relationships) are breaking during a full refresh. When this happens, Power BI keeps the last valid model state, so visuals continue to show old data. Manual table refresh works because it only executes Power Query (M) and doesn’t validate the full model.
To fix this, resolve all model warnings/errors: correct DAX references, ensure columns/tables exist, and fix data type mismatches (e.g., in SWITCH). Also review relationships and remove any broken dependencies. As a check, temporarily disable calculated tables/columns and run Refresh All, if new data appears, the issue is confirmed in model logic. Once all errors are fixed, clear cache, refresh again, and republish to the Service. After the model processes without warnings, new data will appear correctly.
Thank you for using the Microsoft Fabric Community Forum.
Hi chelly911 ,
Thanks for reaching to community, will happy to assists.
As you mentioned refresh all doesn't affecting report update to get the new data. Below are cause and fixes you can try.
This behavior usually points to a difference between Power Query refresh vs model refresh in Power BI.
What’s really happening:
- Manual table refresh (Power Query Editor) → fetches fresh data directly from source → you see new rows
- Refresh All / Service refresh → refreshes the entire model, including relationships, DAX, and dependencies
If there are model-level issues (relationships, calculated tables/columns, or dependencies), the refresh can complete but still result in:
- Old data being shown
- Or model not updating correctly in visuals
Most likely causes in your case:
- Broken dependencies in model
- Errors like “column/table not found” indicate something is failing during full model processing
- This can prevent proper data propagation even if refresh “succeeds”
- Calculated tables / columns
- These are only recalculated during full refresh (not per-table preview)
- If they fail, they can block or distort results
- Relationship or filter issues
- New rows may not appear if relationships/filter context exclude them
- Incremental refresh / partitions (if used)
- Only certain partitions refresh → new data might not be include
What to check:
As per refresh warnings in the power bi. It looks like some visuals/Dax measures are breaking and model get stop the refresh after encountring the error.
- Validate calculated tables/columns
- Check model relationships and filters
- Review incremental refresh settings (if any)
- Fix the reported errors (they do matter, but not because of load)
Power BI sometimes treats these as non-blocking warnings, so refresh completes but results are inconsistent. Tha't why like it's not returned as an error but data is not updating in the report.
Hope this helps! Please consider this as an accepted solution if it is work for you.
I misexplained it when I manually refresh the tables in Power BI Desktop, I get the new rows. However, when I use “Refresh All” in Power BI Desktop or refresh in the Service, the new rows do not appear.