Forum Discussion
Dataflow Gen2: Variable Library references fail in Connection Settings
This appears to be a screenshot of an error shown in the data preview of the Power Query editor.
When using Variable.ValueOrDefault the value being used for the data preview today is the "Default". What could be happening is something related to the value that you have as default and how that is being passed into the M code. Perhaps there's something quite specific with the Lakehouse connector that returns this error or it could also be that your queries where you store your variables are set to staging hence it's actually not a scalar value but rather a table. Based on the screenshot, it does appear that both your queries are set to be staged hence it might actually field during a refresh as the values wouldn't be rendered as simple values and they'll be basically just a value within a table of a single column
Regardless, I'd recommend opening a support ticket so we can take a closer look at this behavior. Feel free to share the case number with me directly so I can take a closer look
Would you mind sharing a screenshot of the error or failure that you're seeing ?
I have this :
In my Advanced Editor query, I have several transformation steps (adding new columns, renaming, etc.) and a merge with other queries.
When I update the parameters using the Variable Library, all transformation steps work correctly, except the Merge step, which fails.
The merge returns the following error: “DataFormat.Error: There is no valid Delta table at this location.”
This appears to be a screenshot of an error shown in the data preview of the Power Query editor.
When using Variable.ValueOrDefault the value being used for the data preview today is the "Default". What could be happening is something related to the value that you have as default and how that is being passed into the M code. Perhaps there's something quite specific with the Lakehouse connector that returns this error or it could also be that your queries where you store your variables are set to staging hence it's actually not a scalar value but rather a table. Based on the screenshot, it does appear that both your queries are set to be staged hence it might actually field during a refresh as the values wouldn't be rendered as simple values and they'll be basically just a value within a table of a single column
Regardless, I'd recommend opening a support ticket so we can take a closer look at this behavior. Feel free to share the case number with me directly so I can take a closer look