This forum describes the known issues and limitation of Power BI Service that may impact Power BI usage in InfoBurst.
Power BI Reports
Filtering
The Power BI SDK does not support reporting of available Report table(s) and fields. When creating a Burst where the Power BI Report is to be filtered, the InfoBurst user must precisely define the target Table and Field names. Invalid Table/Field names will result in unfiltered output from Power BI. See the Single-Pass Bursting > Power BI Reports section of the following article for details:
A Paginated Report can be embedded within a Report. Currently, Power BI does not support publication of such a Report where the embedded Paginated content is visible. The published file contains the following message in place of the embedded content:
The limitation is described in the following Microsoft article:
Microsoft limits the Export of a Paginated Report (includes report refresh and publication) to 60 minutes. The limitation is described in the following Microsoft article:
Microsoft does not support Export of a Paginated Report that uses SSO to Azure Analysis Services. The limitation is described in the following Microsoft article:
Export of a Power BI Report or Paginated Report to file (PDF, Excel, etc.) takes approximately 20 seconds. This appears to be by design and does not vary based on size of Fabric Capacity license. This behavior may significantly increase Burst runtime in a high-volume bursting scenario.
Example: Bursting of a single Power BI Report for 500 values would take approximately five hours.
Semantic Models
Data Volume
InfoBurst can publish a Semantic Model to Power BI. When the number of rows in the Semantic Model exceeds 1M rows, Power BI rejects the upload request. This is a know restriction of the Power IB SDK. Details in the following forum:
A Semantic Model created by InfoBurst cannot be used with a Power BI Datamart or Dataflow. This is a Microsoft restriction and is described in the following forum:
Bryan Baca
This forum describes the known issues and limitation of Power BI Service that may impact Power BI usage in InfoBurst.
Power BI Reports
Filtering
The Power BI SDK does not support reporting of available Report table(s) and fields. When creating a Burst where the Power BI Report is to be filtered, the InfoBurst user must precisely define the target Table and Field names. Invalid Table/Field names will result in unfiltered output from Power BI. See the Single-Pass Bursting > Power BI Reports section of the following article for details:
https://help.infosol.com/en/support/solutions/articles/19000022695-bursting-methods
Embedded Paginated Reports
A Paginated Report can be embedded within a Report. Currently, Power BI does not support publication of such a Report where the embedded Paginated content is visible. The published file contains the following message in place of the embedded content:
The limitation is described in the following Microsoft article:
https://learn.microsoft.com/en-us/power-bi/collaborate-share/end-user-pdf?tabs=powerbi-service#visuals-that-arent-supported
Considerations and limitations
The following Microsoft article describes all limitations for Power BI Report Export:
https://learn.microsoft.com/en-us/power-bi/developer/embedded/export-to#considerations-and-limitations
Power BI Paginated Reports
Export Time
Microsoft limits the Export of a Paginated Report (includes report refresh and publication) to 60 minutes. The limitation is described in the following Microsoft article:
https://learn.microsoft.com/en-us/power-bi/developer/embedded/export-paginated-report
Analysis Services SSO
Microsoft does not support Export of a Paginated Report that uses SSO to Azure Analysis Services. The limitation is described in the following Microsoft article:
https://learn.microsoft.com/en-us/power-bi/developer/embedded/export-paginated-report
Considerations and limitations
The following Microsoft article describes all limitations for Power BI Paginated Report Export:
https://learn.microsoft.com/en-us/power-bi/developer/embedded/export-paginated-report#considerations-and-limitations
Export Times
Export of a Power BI Report or Paginated Report to file (PDF, Excel, etc.) takes approximately 20 seconds. This appears to be by design and does not vary based on size of Fabric Capacity license. This behavior may significantly increase Burst runtime in a high-volume bursting scenario.
Example: Bursting of a single Power BI Report for 500 values would take approximately five hours.
Semantic Models
Data Volume
InfoBurst can publish a Semantic Model to Power BI. When the number of rows in the Semantic Model exceeds 1M rows, Power BI rejects the upload request. This is a know restriction of the Power IB SDK. Details in the following forum:
https://help.infosol.com/support/discussions/topics/19000033619
Datamart/Dataflow Availability
A Semantic Model created by InfoBurst cannot be used with a Power BI Datamart or Dataflow. This is a Microsoft restriction and is described in the following forum:
https://help.infosol.com/support/discussions/topics/19000035632