Materialized Lake View Refresh activity Pipeline bug
Hi all, When using the preview feature refresh mlv activity in the pipeline, is do have some major bugs. After saving, it goes back to default, the pipeline does not want to refresh after, and I cannot parametrize it. Is there any workarround, and is this a known bug? Cause this is not workable.
[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... ThanksCopy Data with VNET gateway error
Hi all, I have an issue with my SQL Server / Azure SQL Database extraction. As you can see I connected to my source using a VNET gateway, and I do see the preview data. This table contains 37 rows but when I try to run the copy activity in my pipeline or a simple copy job, is do get the error: ErrorCode=LakehouseOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Lakehouse operation failed for: Operation returned an invalid status code 'InternalServerError'. Workspace: 'xxxxx'. Path: 'xxxxx/Tables/dbo'. Message: 'Internal Server Error'. TimeStamp: 'Thu, 07 May 2026 06:39:40 GMT'..,Source=Microsoft.DataTransfer.ClientLibrary,''Type=Microsoft.Azure.Storage.Data.Models.ErrorSchemaException,Message=Operation returned an invalid status code 'InternalServerError',Source=Microsoft.DataTransfer.ClientLibrary,' I've tried different lakehouses as destenation, new pipeline, run with query, write as parquet, all the simple stuff, but I still got this message. Is there something I don't get? Hope someone could help me out.
How to fully load data once and then incrementally update with yesterday’s data in Dataflow Gen2?
Hi all, I'm new to Dataflow Gen2 and exploring it to centralize data transformations for Power BI reporting. I’m using F2 capacity and pulling data from multiple sources like SQL Server, Salesforce, and Microsoft Business Central. While building the dataflows, I didn’t define any explicit output data destination (bottom left panel in the dataflow UI). But I noticed that files like “StagingLakehouseForDataflows_...” are automatically getting created in my workspace under type “Lakehouse” or “Warehouse”. What exactly are these files? Is it okay to leave the output destination undefined if I can still see the tables and use them in Power BI? Incremental Refresh Doubts: I tried setting up incremental refresh on one of the queries (Currency Exchange Rate). This table has three columns: Currency Code Starting Date Currency Exchange Rate There’s historical data available from 2020 onwards. Since the exchange rates update daily, my goal is to: Load the full historical dataset initially Then, refresh only yesterday’s data daily (i.e., append new records to the existing dataset) So I used these settings in Incremental Refresh: Date column: Starting Date Extract data from the past: 1 day Bucket size: Day But after enabling and running the refresh, I noticed that only records with yesterday’s date were loaded — the older data (from 2020 onwards) wasn't loaded at all. What I need: I want the dataflow to load the entire dataset initially, and then on each scheduled refresh, only add new records from yesterday (without removing the older ones). How can I properly configure incremental refresh to support this pattern in Dataflow Gen2? Thanks in advance for any help or clarification!
