How to get the internal Page Name and Visual Name for Power Automate
Hi everyone, I am trying to automate a daily Power BI report email using Power Automate. My requirement is: Power BI Report ↓ Power Automate ↓ Export a specific Power BI visual as PNG ↓ Embed the image in an HTML email ↓ Send the email daily I already have an existing Power Automate flow that sends an HTML table successfully. Now I also want to include a Power BI chart below the table in the same email. I am using the Power BI action: "Export To File for Power BI Reports" I have selected: - Workspace - Report - Export Format = PNG The action provides the following fields under Pages: - Pagename - Visualname - Bookmark Name - Bookmark State The Power BI report has a page called "X" and the visual I want to export is called "Y". The problem is that I don't know the INTERNAL page name and INTERNAL visual name required by the Power Automate export action. My Power BI Service URL follows this format: https://app.powerbi.com/groups/<workspace-id>/reports/<report-id>/<some-id>?experience=power-bi Unlike some examples I have seen, the URL does not contain something like: ReportSection123abc I understand that the Power BI API uses an internal page name that is different from the visible page name. My questions are: 1. How can I retrieve the internal page name for page "X" in the current Power BI Service experience? 2. How can I retrieve the internal visualName for visual "Y"? 3. Is there a recommended way to get these values without manually inspecting browser/developer tools? 4. Can I use the Power BI REST API / Get Pages API to retrieve the internal page name and then use that value in Power Automate? 5. Is there a Power BI/Power Automate connector or API that can retrieve the visual names using getVisuals or another method? Any guidance would be greatly appreciated. Thanks!
Previous Month Measures
I have attached a dummy pbix file that loosely resembles a part of my data model in terms of the kinds of visuals I use and measures required. As you can see, I need to add a FY filter in the Filter Pane for both column charts, that way I can manually save and lock down a version at close of business 31st Mar each year, then copy and open a new one for 1st Apr where I amend the FY filter. An issue that I have always struggled with are the 2 Previous Month cards I have highlighted with Red Borders, can someone help me get the previous month's figure? I have tried so many different measures and I can never get the number I want. This would allow me to use conditional formatting to indicate Up / Down trend on Current vs Previous mth etc. Any help will be gratefully received. https://www.dropbox.com/scl/fi/umkrnfgjofj748pjpvwyc/Test.pbix?rlkey=5cso1917a69pnlfof6k9mdclu&st=wrcxmz9d&dl=0incremental refresh policy
Hi Community..!! I am using incremental refresh in the power bi , 1 year data and incremental refresh on 2 days on updated date, we have kept refresh twice a day in power bi workspace, but report is not showing correct order status, if we keep incremental refresh on 3 months on updated date then order status are getting correct but not on 2 days refresh. what will be the issue? does keeping two days on updated date will not work? how the incremental refresh works on updated date? why the data is wrong? Could anyone please help me on this? I am attaching screenshot for your reference. Thanks in advance..!!
[BUG] Dataflow Gen2 destination picker 404 — api.powerbi.com lakehouses UK region
Hi community, We have a complete blocker with Dataflow Gen2 (CI/CD) destination configuration in our UK-region Fabric tenant. The Error: When clicking "Add default destination" and selecting a Fabric Lakehouse from the OneLake catalog, this error fires immediately for ALL users including the workspace Admin: DataSource.Error: Downstream service call to url 'https://api.powerbi.com/v1/workspaces/{WORKSPACE_ID}/lakehouses' failed with status code 404. (Region: uk) The Lakehouse IS visible in the OneLake catalog — it appears in the picker. The 404 fires the moment it is clicked. Root cause hypothesis: The destination picker calls the legacy Power BI REST API: api.powerbi.com/v1/workspaces/{id}/lakehouses ← returns 404 For Fabric-native workspaces in the UK region, the correct endpoint should be: api.fabric.microsoft.com/v1/workspaces/{id}/lakehouses The OneLake catalog listing (which uses a different path) resolves the lakehouse correctly — it's only the destination configuration call that uses the wrong endpoint. Workarounds attempted — all failed: 1. UI — Admin user attempted same steps → same 404 2. queryMetadata.json via Git — Added destination fields, pushed to prod branch → Fabric silently strips loadEnabled/destination on every sync, creating a permanent conflict loop (workspace ≠ Git on every update) 3. Authentication methods — Before the error began firing immediately, a "Connect to default data destination" screen appeared offering two authentication options for the Lakehouse connection: - Organizational account (Sahil Singh / user account) - Service principal Both were attempted. Neither succeeded — the 404 followed in both cases. Subsequently, this connection credentials screen stopped appearing altogether. The 404 now fires immediately upon clicking lh_dhl_prod in the OneLake catalog, before the connection setup dialog is even shown. This regression suggests the failure point has moved earlier in the destination configuration flow. Questions: 1. Is this a known issue for UK-region tenants? 2. Is there a way to configure the Dataflow Gen2 destination via Fabric REST API directly to bypass the broken UI? 3. Are there other file-based approaches (mashup.pq metadata) for CI/CD Dataflow Gen2 destinations? Happy to provide Session IDs and further details to the Fabric team. I have attached the relevant images, PFA... ThanksPower BI Paginated Report publish does not overwrite changes in Power BI Service
Hi everyone, I’m currently working on a project that uses Power BI Paginated Reports. These reports were originally created as standalone paginated reports in Power BI Report Builder. They use their own data sources and datasets/tables, and they are not connected to a Power BI semantic model. Here is the issue I’m experiencing: I download an existing paginated report ( .rdl ) from Power BI Service. I open it locally in Power BI Report Builder. I modify some report properties/content, such as data source, dataset, table, or report configuration. I publish the report back to the same workspace and overwrite the existing report. The publish operation completes successfully, but when I open the report in Power BI Service, the changes are not reflected. It appears as if the previous version is still being used and when ı try download rdl again nothing changes. I expected the normal Publish → Replace/Overwrite workflow to update the existing paginated report.(Like PBI Reports) I found that I can work around the issue by deploying/updating the report through PowerShell, but I’m not sure PowerShell should be necessary for a standard report update. My questions are: Is this expected behavior for paginated reports in Power BI Service? Are there any known limitations with overwriting an existing .rdl from Power BI Report Builder? Could the existing report’s data source, dataset, or embedded configuration prevent the uploaded .rdl from fully replacing it? Is there any caching, report binding, or artifact metadata in Power BI Service that could cause the old version to remain active after publishing? What is the recommended deployment approach for this scenario: normal Report Builder publishing, REST API/PowerShell, or another method? I would prefer to use the standard publish and overwrite workflow if possible, rather than maintaining a separate PowerShell deployment process. Thanks in advance.
Hide/Unhide 2 visuals based on multiple slicers
###Urgent Hi community, I'm trying to implement a show/hide logic for a report page based on mandatory slicer selections and would appreciate some guidance. Slicer details: ID - Table 1 Date - Table2 Run_var - Table 3 Run_var_value - Table 3 Description - Table 5 I have 3 table visuals. Visual 1 Visual 2 Visual 3 Visual 3 has a different filter requirement than Visual 1 and Visual 2. Run_var and Run_var_value are required only for Visual 1 and Visual 2. Description is required only for Visual 3. The requirement is that, the data in these visuals must appear only when all the necessary slicers are selected else it must not show any data at all. To achieve this I used the following dax and flagged the result. The DAX works correctly in a Card visual but not consistently when used as a visual-level filter on table visuals The table sometimes displays data even when all mandatory slicers are not selected. I need to validate both conditions: Mandatory slicers have been selected. The selected values form a valid combination in the data model. The final requirement is to ensure that the visuals display data only when all required slicers for that specific visual have been selected; otherwise, the visual should remain completely blank.Neither COALESCE nor "+ 0" working in Multi-row Card to convert Blank to 0
Good Afternoon, I have the following Multi-row card visual, where I have placed three measures: Unfortunately the second measure is displaying a blank (highlighted with a red cross above) :-(.... When I tried modifying the second measure to either use COALESCE or "+ 0", it made no difference and still blank appeared...But then when I trialled "+ 10", it did actually show 10 ! Kindly advise...
