Forum Discussion
Visuals with calculated columns/tables fail during semantic model refresh
Hi suparnababu8
Thanks for the links. I think they will help me to make it more optimized during the refresh.
After some investigations, I realized that not just calculated columns/tables, also the relationships get broken during semantic model refresh, if a visual uses several tables with relationship.
I did some experiments and I realized that the problem was because I chose "partial batch" as commit mode. This was causing the tables under process to not function in the report. Previously, I was not able to use "transactional" commit mode due to memory issues since I was trying to process all tables in one semantic model refresh activity.
Now I tried using 3 different semantic model refresh activites with "transactional" commit mode connected together and they refresh different tables in semantic model to decrease the load on memory at an instant time. This solved my problem and currently no visuals fail in my report during any of these semantic model refresh activities. I don't exactly know how "partial batch" causes these problems in report but for now, "transactional" commit mode solved my problem.
Thanks again for your comment!
Super User
I recommend you create that calculated column in Power Query and try to refresh again. Could you please go through below urls which might hels you
Solved: Report refresh and calculated column changes takes... - Microsoft Fabric Community
Incremental refresh for semantic models in Power BI - Power BI | Microsoft Learn
Refresh Power BI Semantic Model After Dataflow Automatically - RADACAD
Thanks!
Hi suparnababu8
Thanks for the links. I think they will help me to make it more optimized during the refresh.
After some investigations, I realized that not just calculated columns/tables, also the relationships get broken during semantic model refresh, if a visual uses several tables with relationship.
I did some experiments and I realized that the problem was because I chose "partial batch" as commit mode. This was causing the tables under process to not function in the report. Previously, I was not able to use "transactional" commit mode due to memory issues since I was trying to process all tables in one semantic model refresh activity.
Now I tried using 3 different semantic model refresh activites with "transactional" commit mode connected together and they refresh different tables in semantic model to decrease the load on memory at an instant time. This solved my problem and currently no visuals fail in my report during any of these semantic model refresh activities. I don't exactly know how "partial batch" causes these problems in report but for now, "transactional" commit mode solved my problem.
Thanks again for your comment!