Limitations and specifications

Last update: Wed Feb 16 2022 00:00:00 GMT+0000 (Coordinated Universal Time)

Topics:
Report Builder

CREATED FOR:

User
Admin

Power BI publishing restrictions section_D4BDD70B20F94A0FAE53531CA528AE42

NOTE

These restrictions apply only to the option “Publish Report Builder Requests as Power BI Dataset Tables”.

A maximum of 100 Report Builder requests can be exported to Power BI per workbook.
The scheduling process will stop exporting requests when the 101th request is reached.
Only the first 10,000 rows of Analytics data will be sent to Power BI per Report Builder request. The remaining rows will be ignored.

Edit a Report Builder request after publishing to Power BI section_6989E74F68DD43F08D37C36B6777DB50

NOTE

This specification applies to the options “Publish All Report Builder Requests as Power BI Dataset Tables” and “Publish All Formatted Tables in the Workbook as Power BI Dataset Tables”.

Editing a Report Builder request after publishing it to Power BI may cause problems.

Case 1: You publish a workbook to Power BI and create a visualization based on its data. Next, you make changes to the workbook, causing one of the columns of the data set that it references to disappear. Then you republish. This will break the visualization in Power BI.

Here is an example of how the visualization WILL break:
1. In Report Builder, create a workbook with one request, using the Page dimension and the Page Views metric.
2. Schedule this requestto be published to Power BI.
3. In Power BI, create a visualization for Page and Page Views.
4. Now edit the workbook by removing Page Views from the request.
5. Edit the schedule with the updated workbook and re-publish the request to Power BI.
6. Once the new workbook is sent to Power BI
  1. Verify that it overwrote the existing dataset that was created when you first published.
  2. Verify that the page_1 table is properly updated with the Page and Visits columns.
  3. Verify that your visualization is broken, since it references the Page Views column that is no longer present in the page_1 table.
Here is an example of how the visualization will NOT break:
1. In Report Builder, create a workbook with one request, using the Page dimension and the Page Views metric.
2. Schedule this request to be published to Power BI.
3. In Power BI, create a visualization for Page and Page Views.
4. Now edit the workbook in Report Builder, adding the Visit metric while keeping Page and Page Views.
5. Edit the schedule with the updated workbook and re-publish the request to Power BI.
6. Once the new workbook is sent to Power BI
  1. Verify that it overwrote the existing dataset that was created when you first published.
  2. Verify that the page_1 table is properly updated with the Page, Page Views, and Visits columns.
  3. Verify that your visualization continues to work properly, since it references two columns that are still present in the page_1 table.
Case 2: You pin a section of your workbook to a dashboard in Power BI and you later remove that pinned section (such as a chart or a table) from the workbook. This will break the visualization.

Change the name of a Power BI report section_2E7893A78B914EBFACB2B08CBD9E472E

By default, the name will be populated from the workbook filename (without the .xlsx extension), except that spaces are replaced with underscore characters.

Keep in mind that

The label cannot be a combination of letters and numbers that could be mistaken for a row and column address. For example, A100 cannot be a label because it is the address of a cell in a worksheet.
The following characters are not valid label characters: '#', '@', '!', '$', '^', '&', '*', '', and '~', ' ' . They are replaced by an underscore character.
When you enter an invalid name, a warning message will be shown that will suggest an auto-generated name. If you click Yes, this name will be used. If you click No, the Advanced Wizard UI will let you enter the new name.

recommendation-more-help

a83f8947-1ec6-4156-b2fc-94b5551b3efc