Forum Discussion
Table copied from directquery is not updating
- 10 months ago
Hi Testeri,
I am not sure how it will works for your business requirement but I am doing this,
1. Open your report on desktop application which is connected to other semantic model/self-serve from Power BI service.
2. Switch from “Live” to DirectQuery for PBI dataset and Analysis Services mode.
3. Now you can create local calculated tables and merge them with imported or other data sources.
4. This will helps you to keep live data connection and creating your own local DAX tables.Else, if your transformations are complex, Instead of connecting live, import the semantic model’s data using Analyze in Excel / DAX query export then bring that into Power BI as an import model. You will get full control and can create all tables, measures, and columns freely.
Thanks,
If you found this solution helpful, please consider giving it a Like👍 and marking it as Accepted Solution✔. This helps improve visibility for others who may be encountering/facing same questions/issues. - 10 months ago
When you create copies of tables from a semantic model in Power BI Desktop (like Copied_table_A = Semantic_table_A), these copied tables are calculated tables that are evaluated only during data refreshes. If your copied tables have not updated for a long time but new copies work fine, the most likely causes are:
The original copied tables are not refreshing properly due to cache or metadata sync issues with the semantic model.
There may be schema changes or column renames in the semantic model that break the copied tables, preventing refresh.
Power BI sometimes does not automatically detect changes in calculated tables referencing a semantic model, so manual refresh or model metadata refresh is needed.
The refresh process might be incomplete or failing silently, leaving old data in place.
How to fix this:
Open Power BI Desktop, go to the semantic model tables view, and click the refresh icon in the model editing pane to force metadata and data sync.
If refresh issues persist, delete and recreate the copied tables, as you noticed new copies update correctly.
Regularly check for schema changes in the semantic model and update your copied tables accordingly.
Ensure your dataset refresh completes successfully without errors in both Desktop and Service.
Alternatively, consider using calculated columns or measures on original tables instead of copying whole tables for added columns, reducing refresh complexity.
Hi and thanks ajaybabuinturi for the info.
Are there any information that will it return to like it was? Current method means that you have to create tables every day again and again and create additional columns to those and change all measures related to copied tables. Not very reasonable...
So how should I handle situation when directquery semantic table is needed for "template" and then need to add own columns to it and the table needs to be up to date when data refreshes? There must be many users that have to do what I have to do.
Does this current way affect only Desktop app? Will the Service scheduled refresh still work in the future like it does now?
Hi Testeri,
I am not sure how it will works for your business requirement but I am doing this,
1. Open your report on desktop application which is connected to other semantic model/self-serve from Power BI service.
2. Switch from “Live” to DirectQuery for PBI dataset and Analysis Services mode.
3. Now you can create local calculated tables and merge them with imported or other data sources.
4. This will helps you to keep live data connection and creating your own local DAX tables.
Else, if your transformations are complex, Instead of connecting live, import the semantic model’s data using Analyze in Excel / DAX query export then bring that into Power BI as an import model. You will get full control and can create all tables, measures, and columns freely.
Thanks,
If you found this solution helpful, please consider giving it a Like👍 and marking it as Accepted Solution✔. This helps improve visibility for others who may be encountering/facing same questions/issues.