Fabric > Dataflow Gen 2 > Destination: Allow this to be a dataflow parameter like table name can be
I recently disovered parameters in dataflow which was a big unlock in organization/efficiency, but not being able to specify the detination dynamically (outside of very end table name) nullifies that features' usefulness by having to make at least one per lakehouse because of this. Please update the Destination UI to allow a Parameter to be selected for the lakehouse (including folder/schema/dbo) to be populated by a dataflow parameter.
4 Comments
- miguel
Community Admin
Status changed:NewtoAbandonedSome connectors may have a way to pass parameters to the resource path that do not affect which connection is bound to it.
Nevertheless, from a purely practical standpoint we do have the "advanced editor" within the Dataflow UI where you can pass any identifiers to the navigation steps of a data destination and pass your own workspaceId and such. More information can be found here:
https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-advanced-edit-data-destinations
miguel Edit: I see advanced editor of destination now after enabling that option. My bug report and suggestion still stands though: bug: in the UI-based (non-advanced) it allows you to set a parameter as the target table, but it does not work passing that parameter via a pipeline, suggestion: have a parameter for the workspace as well in the ui-based (non-advanced) destination selector.
Advanced Editor has nothing to do with data destination - only the Query. This is Dataflow Gen 2.- miguel
TylerHilliard would you mind sharing with us where the feature from the article shared fell short for you?
Just to confirm, it is in the context of a data destination., but do feel free to suggest any improvements to the article in case the wording wasn't clear.
- miguel
TylerHilliard hey! sorry. I don't get any notifications when a comment has been edited, but i'm only noticing the change now.
The capability that you're mentioning is available today. When you select a source that supports parameters then it fundamentally has the UI that allows you pass them. Here's a screenshot on how that looks like:You can see all the available options to bind a value to it through the UI.
If perhaps there's something amiss with a specific connector (like the Lakehouse connector not accepting parameters), please do feel free to raise this request to expose specific paramaters to the specific connector or data source of your choice as a new idea.
