Dataflow Gen2: Variable Library references fail in Connection Settings
Hi everyone, I am working on variabilizing my Dataflow Gen2 for deployment pipelines, following the documentation on Variable references. I’ve noticed a discrepancy in how variables are handled, and I suspect it might be a bug or a UI limitation. The Issue: When I define parameters using a Blank Query and try to use them to replace values in the Source Connection settings (via the user interface), the connection fails or isn't recognized. And replace in the source: let Source = Lakehouse.Contents([]), #"Navigation 1" = Source{[workspaceId = workspace_id]}[Data], #"Navigation 2" = #"Navigation 1"{[lakehouseId = lakehouse_id]}[Data], #"Navigation 3" = #"Navigation 2"{[Id = "Table1", ItemKind = "Table"]}[Data] in #"Navigation 3" That's not working. The Workaround (Manual M Code): However, if I bypass the UI and manually insert the Variable.ValueOrDefault syntax directly into the Source Step using the Advanced Editor, it works perfectly. let Source = Lakehouse.Contents([]), // Retrieving variables manually works fine workspace_id = Variable.ValueOrDefault("$(/**/My Library/Workspace ID)", "default_value"), lakehouse_id = Variable.ValueOrDefault("$(/**/My Library/Lakehouse ID)", "default_value"), #"Navigation 1" = Source{[workspaceId = workspace_id]}[Data], #"Navigation 2" = #"Navigation 1"{[lakehouseId = lakehouse_id]}[Data], #"Navigation 3" = #"Navigation 2"{[Id = "Table1", ItemKind = "Table"]}[Data] in #"Navigation 3" My Question: Has anyone else encountered this issue where the UI connection dialog doesn't seem to parse the variable reference, forcing us to hardcode M logic manually? Is there a specific syntax for the UI that differs from the Advanced Editor? Thanks for your help! References: - Dataflow Gen2 Variable Library Integration
A Typo in the new parameter window of Dataflow Gen2 (Korean)
Hi Team, When I tried to create a parameter in the Dataflow Gen2, I noticed a typo in the new parameter window: 어느하나라도 The labels were different from Power BI Desktop. In Dataflow Gen2, that should be modified as follows. 어느하나라도(Any) -> 임의 Korean English Power Query editor (Power BI Desktop 2.146.705.0 64-bit (August 2025)) Korean English Thanks, HongA Typo when removing rows in Dataflow Gen2 (Korean)
A Typo when removing rows in Dataflow Gen2 (Korean) Hi Team, When I tried to remove alternate rows in Dataflow Gen2, I noticed the label was different from Power BI Desktop: “대체 행 제거” We believe that “교대로 행 삭제” is easier to understand. In Dataflow Gen2, I think that should be “교대로 행 삭제”. Korean English Power Query editor (Power BI Desktop 2.146.705.0 64-bit (August 2025)) Korean English Thanks, HongA Typo about extract in the Dataflow Gen2 (Korean)
Hi Team, When I tried to transform and add a column in the Dataflow Gen2, I noticed a typo about extract: “압축 풀기”. That should be “추출”. Korean English In Power BI Desktop(Version: 2.145.1602.0 64-bit (July 2025)), we can see “추출”(Extract). Korean English Thanks, HongDataflow Gen2 Destination: Columns Name
So I've been using a table in a Fabric WH for some months now which includes a column name "Customer No.". Now I wanted to append from a differenct dataflow to that table and i get an error claiming this table has unsupported column names: It is extremly unfortunate if such constraints are being added afterwards... and therefore breaking things that have been working!
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?
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.
Data flow refresh error
When i try to create the data flow gen 02 from data lakehouse to data warehouse, after i published i'm getting an error "TridentLakeClientUserException, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Failed to insert a table., InnerException: Unable to create a table on the Lakehouse SQL catalog due to metadata refresh failure, for Lakehouse Id: #{0} and Batch Id: #{1}. underlying error code: '#{2}', error: #{3}, Underlying error: Unable to create a table on the Lakehouse SQL catalog due to metadata refresh failure, for Lakehouse Id............................." My case i don't have the empty column and I coudn't find any data type errors.
