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!
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!
Community SupportHi FabricEngineer ,
Glad to hear that the issue with the semantic model refresh has been resolved.
The "partial batch" commit mode seemed to be causing problems with relationships and calculated columns/tables, likely due to incomplete data commits. By splitting the refresh into multiple activities with "transactional" commit mode, the memory load has been reduced and model has remained consistent, which appears to have resolved the errors.
It’s good to know everything is working smoothly now.
If any further assistance is needed, feel free to reach out.
It might be helpful to explore these additional resources to further optimize your refresh process and troubleshoot any potential issues:
Troubleshoot refresh scenarios - Power BI | Microsoft Learn
Incremental refresh for semantic models in Power BI - Power BI | Microsoft Learn
Please mark your solution or any other helpful responses as "Accept as Solution" to assist others with similar queries.
Best Regards,
Vinay.