Power BI Embedded feature: Customize end user’s error experience for embedded reports
Updated: September 10, 2018
Software engineers can now customize the error experience shown when a report fails to load or is not available to the end user at that moment. Instead of the default Power BI error page (shown below), add anything you want—a pop-up message, an entire page with your native application design, or custom action buttons—to bring the user back to the application flow.
Here is a basic example of a different error page instead of the default error:
There are many errors that can occur, and not all of them are on the same severity level. For example, when a report fails to load, the user can’t do anything with the report. If an operation on the report (such as export data) fails, the user should be notified but can continue to use the report. To address that, we've added a level property, indicating the type of error that occurred. Each level refers to a different group of errors. The Fatal level, for example, means the report failed to load completely and the user can’t interact with anything. You can handle different types of errors by using the level property, giving the user the appropriate context for the error.
The override feature is available for embedded reports only.