We are encountering an issue where the Power Automate button clicked in Power BI does not provide the expected groupId or datasetId in its output, resulting in an empty body.entity object ({"entity": {}}). This prevents us from creating a dynamic Power Automate flow to refresh a dataset based on the report’s context, this is happening in a Government Community Cloud (GCC) Premium workspace. Despite extensive troubleshooting, the issue persists, and we need assistance to determine if this is a GCC limitation, a bug, or a configuration we’ve missed.
Environment:
- Power BI Tenant: GCC (app.powerbigov.us)
- Workspace: Premium capacity
- Dataset: Import mode, connected to a SQL Server data source
- Power Automate: Linked via Power Automate visual in Power BI Service
- Date of Issue: Ongoing as of March 18, 2025
Goal:
To create a reusable Power Automate flow triggered by a button in a Power BI report that dynamically refreshes the report’s dataset using the workspace and dataset IDs passed by the
Power BI button clicked trigger.
Steps Taken:
- Initial Setup:
- Added a Power Automate visual to a report in Power BI Desktop.
- Created a flow with the Power BI button clicked trigger, initialized variables with triggerOutputs()?['body']['entity']['groupId'] and datasetId, and used these in a Power BI – Refresh a dataset action.
- Published to the Premium workspace and tested in Power BI Service.
- Result: Error—“property ‘groupId/datasetId’ doesn’t exist”—prompting further investigation.
- Output Inspection:
- Added a Compose action with triggerOutputs() to debug the trigger output.
- Output: Detailed headers (e.g., user info, GCC URLs like usgovtexas.logic.azure.us), but body contains only {"entity": {}}.
- Confirmed the flow triggers, but no workspace/dataset metadata is passed.
- Visual and Report Validation:
- Recreated the Power Automate visual, republished the report, and tested in the Service.
- Added dataset fields (e.g., SQL Server columns) to the visual’s field well to provide context.
- Tested with a new report using a simple CSV dataset in the same Premium workspace.
- Result: Output remains {"entity": {}} in all cases.
- Environment Checks:
- Verified the dataset is import-mode, refreshable manually in the Service, and tied to the report (confirmed via Settings).
- Ensured contributor access to the workspace and valid SQL Server credentials.
- Tested in Power BI Service (not Desktop) to rule out simulation issues.
- Flow Variations:
- Tried triggerOutputs()?['body'] and triggerBody() to capture any hidden context.
- Created a new flow with hardcoded IDs—refresh worked, proving the Refresh a dataset action functions when IDs are provided manually.
- Hypothesis Testing:
- Suspected GCC restrictions or Premium configuration issues.
- No tenant settings found to enable/disable this behavior (admin access pending confirmation)
Expected: body.entity to include metadata - groupId, datasetId, etc., per Microsoft documentation.
Stuck: Unable to dynamically retrieve workspace and dataset IDs, forcing manual ID entry, which defeats the goal of a reusable flow.
Any help is greatly appreciated! Thank you!
