March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch 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.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
37 | |
22 | |
20 | |
10 | |
9 |
User | Count |
---|---|
60 | |
56 | |
22 | |
14 | |
12 |