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 UserHi. That's strange. Can you make sure the semantic model is refreshing in desktop or service now? I'm thinking a column could have been removed and now a calculated table is failing. Let's check if other places works and it's something about the new activity or if it has a failure.
I hope that helps,
Hi ibarrau
The semantic model is refreshing properly on partial batch commit mode, which lasts around 10 mins. During that time the visuals with calculated columns break. But once the refresh is completed, then the report visuals work properly again. The tables and column definitions are the same as I checked.