[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... Thanks
left join dax
I have two tables store and clients; no relations between them. I must not have physical relationship, I prefer virtual. And the report have a many slicers: Year, region, country from clients. So the visual have four columns. region (clients) Country (clients) sales (clients) inventory (store) and table store have year region Country inventory Dax measure: NATURALLEFTOUTERJOIN (store, clients) The principal idea is inventory is actually a measure (e.g. left outer join) to get the total in each sublevel: country, region passing the selected value from slicer. Actually I get the total from all years in measure "inventory". I don't get the context to compute (left outer join) :( . I figure out is about the missing relation between tables. Any ideas? thanks in advance.
Cards visual with reference labels on
I am trying to create the simple card visuals with reference labels on , i need to get this reference label to be show from right of card , but i am getting bottom of the main card value. i dont have reference alignment options in my power bi desktop even though i am on latest version.
exportToFile: reportLevelFilters AND a single-select slicer's default value → empty page
**Setup:** Power BI Service, workspace on Fabric capacity (not PPU). Export via `exportToFile` (PPTX) from Power Automate. Server-side only — no JavaScript embedding, so `bookmarksManager.capture()` and `report.reset()` are not available to me. Report-level filters work correctly on pages without slicers on the filtered column. **Problem:** on a page with a slicer that has **Require single selection** enabled, the slicer keeps its saved default value, and my filter is applied on top of it. Since both conditions target the same column and the values differ, the intersection is empty and the page exports blank. "powerBIReportConfiguration": { "pages": [ { "pageName": "ReportSectionXXXX" } ], "reportLevelFilters": [ { "filter": "MyTable/MyColumn eq 'A'" } ] } Slicer default is `'B'`. Result: empty page. The only value that exports correctly is `'B'` —the one the slicer already holds. I understand *why* this happens: a report-level filter narrows the values available to a slicer but never changes the slicer's selection, and preexisting filters combine with the new filter using AND. With single selection enabled, the slicer can never be cleared, so the conflict is unavoidable from the report's default state. **What I'm asking:** is there anything on the API side that resolves this without editing the report? Can `defaultBookmark` or `pages[].bookmark` override the slicer's selection during export, or is single selection a formatting property of the visual that a bookmark cannot affect? 2. Is the precedence between a bookmark and `reportLevelFilters` documented anywhere? The only statement I've found is that export filters are applied *in addition to* the current report state, which reads as AND. 3. Is there any payload option that exports a page as if the slicer weren't there — a server-side equivalent of `report.reset()`? 4. Would moving the field into the "Filters on this report" pane change how the export resolves the conflict? If the answer is "no API-side option exists", a confirmation I can point to would already help — the remaining path is a report-side change (disabling single selection, or an export-only copy of ,the page without the slicer)
Color Coding Issue
I have a PBI report in which I am using a tree map visual and I have coded few brands but for rest which i dint coded is having duplicate color issue, I am searching for a optimised solution for color coding where instead of doing it manually i can do it in some other optimised way.Single dropdown slicer to switch between two Matrix visuals with different hierarchies?
How can I use a single dropdown slicer to switch between two Matrix visuals with different column hierarchies? I have two Matrix visuals that are positioned exactly on top of each other, and I currently use bookmarks to show/hide them. Matrix 1 – MoM: Columns = QTR → Month → Product Matrix 2 – QoQ: Columns = QTR → Product Currently: MoM bookmark → shows Matrix 1 and hides Matrix 2 QoQ bookmark → shows Matrix 2 and hides Matrix 1 I want to replace the bookmark buttons with a single-select dropdown slicer containing: MoM QoQ Expected behavior: Select MoM → Matrix 1 should be visible and Matrix 2 hidden Select QoQ → Matrix 2 should be visible and Matrix 1 hidden Since the two Matrix visuals have different column structures, I cannot simply use one Matrix with the same hierarchy. Is there a native Power BI way to make a dropdown slicer control the visibility of these two overlapping Matrix visuals or trigger the corresponding bookmark? If not, what would be the cleanest workaround while keeping both Matrix structures?
Prep Data for AI changes not reflected in Power BI Service after publishing
I’m using the Prep Data for AI preview feature in Power BI Desktop. I updated both the Simplify Data Schema configuration and the AI Instructions, saved the file, and published it to a development workspace. After publishing, I opened the semantic model in Power BI Service and selected Prep Data for AI. However, the changes made in Desktop do not appear in the Service. The AI instructions are missing, and the Simplify Data Schema adjustments do not seem to have been applied. Troubleshooting performed I have tried the following: Used different versions of Power BI Desktop. Tested both PBIX and PBIP file formats. Published the semantic model to different workspaces. Published it under a different name. Applied the same AI instructions to a completely different semantic model. The instructions appeared correctly for that model, which suggests the issue may be specific to the current semantic model. Question Are there any known limitations or model-specific conditions that could prevent Prep Data for AI settings from being published or displayed in Power BI Service? Are there any additional model settings, metadata, permissions, or diagnostic steps I should check to determine why these configurations are not being retained for this particular semantic model?
