Forum Discussion

Flypigeon0929's avatar
Flypigeon0929
Regular Visitor
5 days ago
Solved

Composite model Refresh issue

Hi guys, I wanted to consolidate 3 power bi reports into one, following it i used the live connection semantic model top get data, after that adding another report, it converted the live connection ...
Need Help
power bi
Tips and Tricks
  • Shubham_rai955's avatar
    Shubham_rai955
    18 hours ago

    This is expected behavior with composite models. Refreshing the consolidated semantic model does not automatically refresh the three original semantic models.

    I would suggest checking these things:

    1. Check the refresh history of all three source semantic models. Make sure their scheduled refreshes are completing successfully.
    2. Check whether query caching is enabled on the consolidated semantic model. Disable it temporarily and test again.
    3. Check for calculated tables based on remote tables, as these may need their own refresh.
    4. After refreshing, republish the report and verify that the Power BI App is showing the latest version.

    Important: If the three reports use different semantic models, you need to manage their refresh schedules independently. The 1-second refresh of your consolidated model does not mean the source data has been refreshed.

jubinsoni's avatar
jubinsoni
Icon for Solution Sage rankSolution Sage
4 days ago

Hi Flypigeon0929​,

ShahRukhSameer's explanation fits what you see: the composite model has nothing of its own to import from those sources, so its refresh finishes in about a second, and the data you see depends on the three original semantic models.

To find out why the numbers look old, I'd check three places in this order:

1. Each original semantic model -> Refresh history: when did the last refresh finish?
2. The composite model's settings -> Query caching: is it set to On? If so, switch to Off (or refresh) and retest
3. Report in the app -> hard-refresh the browser; check the app is updated to the latest published report

Also, your business requirement (all three summary pages scrolling in one report) doesn't need a composite model if the three reports use the same semantic model. In that case, one report pointing at that single model with the three summary layouts on one tall page works, and there's nothing to refresh separately. If they are three different models, the composite approach you built is the right one, and you can make the freshness visible by showing the last-refresh time of each source on the page:

Last Refresh Source A =
FORMAT( MAX( 'Refresh Log A'[RefreshedAtUtc] ), "yyyy-mm-dd HH:mm" ) & " UTC"

That needs a small log or date table that each source model keeps, but it saves a lot of "why is the report old?" questions from the business.

So my overall approach would be:

Check source model refresh history first (composite refresh time is not the data age)
Turn off/refresh query caching on the composite model
Same model for all 3 reports? -> one report, no composite needed
Different models -> keep composite, show last-refresh times on the page

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.