POWER BI QUESTIONS

Why Is Export to Excel Missing in Power BI?

You need the stock figures in Excel for Monday’s warehouse meeting, but Power BI is not offering the export you expected. Now a simple handoff is holding up the review.

PBRS can prepare that workbook and deliver it every week. First, establish why Excel is missing: the answer may be as simple as opening the source report, or it may need a change from the report owner or administrator.

  
THE PROBLEM AND ANSWER

Why the Excel option is missing

The warehouse manager wants to compare stock quantities with the team’s count sheet. The figures are already in Power BI, so exporting them should be the easy part. Instead, the menu offers CSV, or the export option is missing altogether.

Those symptoms have different explanations. Power BI Desktop exports a visual’s data to CSV, and dashboard tiles in the Power BI Service also use CSV. Open the original report in the Service to see the Excel choices available for its visuals. When export is missing there too, report settings, administrator policy or access to the data may be limiting the choice.

That gives you a starting point for today’s workbook. For the weekly meeting, PBRS can export the stock visual to Excel and send it to the warehouse team on a schedule, using the approved account and export settings.

Checks for a missing Excel export option: location, format, export policy and data permissions.

Start with the source report

A dashboard tile offering CSV does not tell you which Excel options are available in the report behind it.

  
YOUR OPTIONS

Get the stock figures into the right workbook

For a one-off stock review, the native export may be all you need. Open the report in the Power BI Service, select the stock visual and look under its export options. A CSV can also be opened in Excel when the team simply needs the figures.

Think about what the warehouse manager will do with the file. A total for each stock item may be enough to compare quantities. Investigating a discrepancy may need the transactions behind that total. Summarized and underlying exports serve those different needs, but underlying export depends on the model, visual and permissions; selecting it does not guarantee every source record.

When the required choice is unavailable, show the report owner the stock visual and explain which figures the team needs. The owner can check the report’s export setting and involve the administrator or model owner where necessary.

Once the team needs the same workbook every Monday, PBRS can take over the repeated preparation. It creates an Excel file from the selected visual and delivers it to the chosen destination. A missing XLSX choice in Desktop does not prevent you from setting up a supported Service export in PBRS, but PBRS does not override a policy that blocks exporting the data.

Export settings and permissions to check

The report owner can allow summarized data, allow summarized and underlying data, or disable export. In Desktop, the setting is under File > Options and settings > Options > Current file > Report settings > Export data. In the Service, a user with edit permission can open the report’s settings. See Microsoft’s export guide.

The administrator should check the tenant’s export and sharing settings, including the groups covered by each setting. Excel, CSV and Excel live connections have separate controls, so an available CSV export does not prove that Excel export is allowed.

Exporting underlying data requires Build permission on the semantic model, as well as support from the report and visual. Build permission is also required for Analyze in Excel. It is not a blanket requirement for every summarized Excel export.

A file for the meeting

The PBRS export described here is an Excel snapshot. Analyze in Excel serves a different need: working in Excel with a live connection to the Power BI model.

  
SET IT UP

Have PBRS prepare Monday’s workbook

Use the stock report to create a single-report schedule in PBRS. Select the Power BI account, workspace and report, then apply the warehouse filter the manager uses for the meeting. Give the stock visual a clear title in Power BI so PBRS can identify it.

Add the delivery destination and choose MS Excel - Data Only (*.xlsx). In the format options, add the report page and select the titled stock visual. Choose summarized or underlying data to match the agreed workbook. You can place the results in an existing Excel template so the team receives them in a familiar worksheet.

Send the first run to yourself or a test recipient. Open the attachment and compare a familiar item’s quantity with the report. Check the warehouse filter, reporting date and expected rows as well. Use the account configured in PBRS for this test, since its access may differ from yours.

When the workbook is right, set the weekly delivery for after the stock data is ready. Monday’s meeting can then begin with the figures already in the team’s inbox.

Visual titles, export limits and the first test

For Power BI Service visual exports, PBRS needs the visual to have a title. Select its page number and visual title in the Excel format options. The PBRS Excel export guide covers templates, formatting and totals.

PBRS documents a maximum of 30,000 rows for its Power BI visual exports to Excel or CSV. DirectQuery’s 16 MB limit can reduce that further. These are the PBRS visual-export limits; the manual Service menu offers different export routes and limits. See the PBRS limitations guide.

Check the expected item count and a record near the end of the export, rather than relying on the file opening successfully. For a larger detailed workbook, consider a paginated report designed for that output. The visual-export limits above do not apply to paginated reports, which have their own requirements.

Check a familiar stock item

A successful delivery proves the file arrived. Comparing its quantities and expected rows with the report tells you whether it is ready for the meeting.

  
FOR DEVELOPERS

Request the workbook from your application

The warehouse application may need to request another copy before an extra stock review. It can run the same tested PBRS schedule, keeping the workbook format, warehouse filter and delivery destination together in PBRS.

The application should track the run and check its result before telling the manager the workbook is ready. The PBRS execution guide explains the full flow.

API example: run the saved Excel schedule

Use the identifier of an existing single-report schedule that already produces the correct workbook. Replace 101 below with that identifier. The request runs the schedule’s configured delivery, so use a test destination during development.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: bearer {pbrsAccessToken}
Content-Type: application/json

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "Warehouse application"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId={ExecutionId}
Authorization: bearer {pbrsAccessToken}

Retain the returned ExecutionId and use it to monitor the run. Inspect the execution result and destination outcome; a completed request alone does not establish that the workbook contains every expected row or has reached a recipient’s inbox. Keep authentication tokens on the backend.

Reuse the tested workbook

The application can request the saved PBRS schedule when another review is needed, using the same export and delivery settings as the weekly run.

  
YOUR NEXT STEP

Start Monday with the workbook ready

The warehouse manager started with a missing Excel option. Finding the cause gets today’s stock figures into the right hands; scheduling the workbook in PBRS takes care of the weekly handoff.

Start with the stock visual the team already uses, confirm the first workbook together, and let PBRS prepare the next one. See how to set up Excel exports, shape the workbook and deliver it for the meeting.

Schedule Power BI reports to Excel with PBRS

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software