Forum Discussion
Error when trying to save changes in embedded report
We have a solution with embedded Power BI reports on a dedicated capacity. We authenticate using a master user so it's a Apps Owns Data scenario. Sometimes when trying to save changed in edit mode we encounter the error ExplorationContainer_FailedToSaveReportDefaultDetails, and it seems rather sporadic. I have a report where saving works in our development environment but not in production.
The detailed message doesn't help much:
"message": "ExplorationContainer_FailedToSaveReportDefaultDetails",
"detailedMessage": "Unable to save the report",
Has anyone experienced something similar?
3 Replies
- AnonymousNot applicable
Hi HeineSkov ,
Base on your description, it seems like you got the issue when saving changes to Power BI reports in production. Could you please check the following info?
- Did you have the proper access to the datasets and workspaces?
- Is there any difference in the report between development and production?
- Check if there are any resource constraints or throttling that might be affecting the ability to save changes: Capacity utilization and throttling
Capacity management improvement and more granularity in the Power BI Premium Capacity Metrics app
Best Regards
- HeineSkovFrequent Visitor
I have access to the datasets and the workspace. We're using a master user, and I have already loaded the report in my browser when I'm editing/saving it.
It's exactly the same report/workspace I'm loading in development and production environment, so there's no differences on the PowerBI side.
It seems very sporadic when I'm able to do it and when I'm not. Sometimes one of my colleagues and I both have the same report open in the browser, and I'm able to save and he's not. Very weird
- AnonymousNot applicable
Hi HeineSkov ,
Based on your feedback, it appears that this issue occurs sporadically and does not relate to your permissions and settings/configurations, as you are able to save successfully at times. It might be caused by network instability or resource overload. Could you please check if the problem persists when only one person performs the save operation at a time?
Best Regards