Skip to content

Power BI Report Cannot Be Displayed

If a Power BI report cannot be loaded in a Business Portals dashboard or page, the portal displays:

Power BI : The content cannot be displayed, please contact the administrator.

This message tells you that the report is unavailable. It does not identify the cause. The technical details are recorded for administrators instead of being displayed to portal users.

For Portal Users

  1. Note which dashboard or page contains the report and when the problem occurred.
  2. Contact your administrator and provide your portal username, the affected page, and the time. A screenshot can help identify the report.
  3. After your administrator confirms that the problem has been addressed, reopen the page to check the report.

Repeatedly refreshing the dashboard does not resolve an access or configuration problem.

For Administrators

  1. Open the Business Portals Administrator Role Center in Business Central.
  2. In Activities, choose Error Logs under Business Portals Logs to open unread errors. Choose Unread Logs instead if you also want to review unread warnings and information.
  3. Find an entry with Source set to Power BI, and check Portal User and the description for the affected report context.
  4. Select the entry and choose Details to read the full message.
  5. Use the details to investigate the problem or pass them to the person responsible for the Power BI setup.
  6. Mark the entry as read after reviewing it. This acknowledges the message; it does not fix the report.

If the entry is not in Error Logs or Unread Logs, return to the Administrator Role Center and choose the Logs action tile in Activities to include messages another administrator has already marked as read. Look for the tile with an icon and no count alongside or below the log cues; it has no separate heading. See Using the Log Cues and Action for the available views. Refresh the log page before checking Occurrence Count and Last Occurred.

Info

Matching failures update an existing entry instead of adding a new row on every dashboard refresh. After an entry is marked as read, matching failures keep it read for 30 minutes. The next matching failure after that period makes it unread again. A different error is shown immediately. See Working with the Log for an example.

If Business Central Cannot Receive the Message

If the portal cannot save the diagnostic message in Business Central, it attempts to save a local log on the portal server. Ask your portal administrator or hosting partner to check this log if no corresponding BC entry appears, or if the occurrence count does not increase even though failures continue.

Power BI local logs rotate when a file reaches approximately 5 MiB, keeping the current file and one previous file for each day. Older output is replaced when both files fill. The portal also removes old log files according to the configured retention period while the application is running. The standard setting is 30 days; your administrator may have configured a different value.

These limits apply to the portal's local Power BI diagnostic files. They do not clear the Business Portals - Log page in Business Central. Review and clear read BC entries separately as described in Working with the Log.