You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature
Allow push down of filtering in Power BI ingestion.
Describe the task
Currently, in the Power BI ingestion pipeline, any workspace (aka project in OM) filters are applied AFTER the metadata was ingested. This causes the issue, that if there are many workspaces in a Power BI tenant, then the API used (https://learn.microsoft.com/en-us/rest/api/power-bi/admin/groups-get-groups-as-admin) to ingest the metadata will hit the API limits very quickly, resulting in timeout and failures.
Feature
Allow push down of filtering in Power BI ingestion.
Describe the task
Currently, in the Power BI ingestion pipeline, any workspace (aka project in OM) filters are applied AFTER the metadata was ingested. This causes the issue, that if there are many workspaces in a Power BI tenant, then the API used (https://learn.microsoft.com/en-us/rest/api/power-bi/admin/groups-get-groups-as-admin) to ingest the metadata will hit the API limits very quickly, resulting in timeout and failures.
The feature request is to allow pushing down the filtering to the Power BI level, but using a different API with an odata filter or something similar - https://learn.microsoft.com/en-us/rest/api/power-bi/groups/get-groups#get-a-list-of-workspaces-using-a-filter-example
The text was updated successfully, but these errors were encountered: