Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hello,
I have a table set up which has fields (timestamp, pointname, value) which was configure in the Query Editor and then set up for incremental refresh / real time data updates. When published I can see new data coming in as desired. So that works. Say this is "Table 1"
Now using Dax, I created a second table "Table 2" which does a Pivot operation on "Table 1" using SUMMARIZECOLUMNS.
When published on the Service, I figured that since the line graph I made of the source table was updating in real time that the line graph I made of the pivoted table "Table 2" would also update in real time. (Page refresh = 30 secs)
But no, the pivoted table line graph only updates if up refresh the dataset manually.
Should this not happen automatically? I would think that a dependent table would recalculate when the underlying table refreshes, but it does not.
Thanks.
Stephen
Solved! Go to Solution.
Hi, @PowerBI-ELM
The calculated tables that have direct queries as their source don't update when the source is automatically updated.
This is just how calculated tables work. They are stored in-memory (like imported tables) and are only updated when you do a refresh operation. If you need realtime data do not use calculated tables, you would have to look at some other option like doing a view in your source database.
For reference:
https://docs.microsoft.com/en-us/power-bi/transform-model/desktop-calculated-tables
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more.
Hi, @PowerBI-ELM
The calculated tables that have direct queries as their source don't update when the source is automatically updated.
This is just how calculated tables work. They are stored in-memory (like imported tables) and are only updated when you do a refresh operation. If you need realtime data do not use calculated tables, you would have to look at some other option like doing a view in your source database.
For reference:
https://docs.microsoft.com/en-us/power-bi/transform-model/desktop-calculated-tables
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more.
I notice the same thing if I create a new table in the Query Editory based on the simpler table that I am refreshing incrementally. I do the pivot in the second table. What I find is that the new data added to first table (when published) does not flow down into the second table.
I figured that would work too.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
58 | |
30 | |
26 | |
21 | |
20 |
User | Count |
---|---|
63 | |
48 | |
24 | |
24 | |
19 |