[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
Gen2 Dataflow to Warehouse - really slow performance
Hi, I'm hitting an issue with loading data from on-prem SQL server to a Fabric Warehouse using dataflows gen2. I'm only moving 34k rows (about 30 columns), and it's taking almost 13 minutes to do this (see image at bottom). Staging is disabled for this (these jobs literally just copy the data as is, with no transformations). If I enable staging, I can see the staging objects load in < 30 seconds, and then it takes 12+ minutes to write from the staging warehouse to the actual real warehouse. If I write the records to a Lakehouse instead of a Warehouse, the whole thing always completes in 30 - 45 seconds. Is this type of performance typical for loading a Warehouse??? Can't believe it is, but the jobs are too simple to have anything messed up I think. Any ideas? Thanks, Scott
Dataflow Gen 2 : Lakehouse connector doesn't work
Hello, It's been days since I try to use the Lakehouse connector with a dataflow gen2. When I try to select the lakehouse I want to connect to, the cursor goes round and round for minutes and I get this error : Do you know if I need to do some complementary configurations to resolve that issue please ? Notes : Both Lakehouse and dataflow originate from the same workspace; I use a trial Fabric
Data Flow Gen 02 refresh error
I have created Data Flow Gen 02 to transfer data from a data lakehouse to a data warehouse, with the data warehouse as the final destination. "There was a problem refreshing the dataflow. Please review the error message(s) below, fix the problem, and try again. (Request ID:). dimdate: Error Code: Mashup Exception Data Source Error, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Microsoft SQL: Internal system error when attempting to open or create remotely stored delta log file. This error is usually intermittent. Please try the operation again and contact Customer Support Services if this persists. Statement ID:" The 'failed reason' table is changing from time to time. Is there a way to fix this issue?
how to merge a referenced table in a dataflow
Hello, I'm totally new on Fabric and I'm creating a dataflow. Anyone knows why is not possible to create a merge with a referenced table? and what would be the workaround? security table at left doesn't appear on the list for the merge. Thank you so much for the answers.Data Flow debugging does not start in IR Virtual Network Mode.
Hello everyone, I have a problem with Integretion runtimes and Managed Private Endpoint, from data flow with my on prem SQL. I followed this official guide link The VPN is ok, I can call my SQL from Azure VM and back. In a my pipiline, test connection to my table in my on prem SQL is ok Only when I need to use my dataset from dataflow, I can't start debugging. Error details: Internal server error executing the request. I can't understand where find more details about the problem.
