Simplify and improve visualisation for variable library importation within pipeline
Hi,
One idea would be to simplify the importation of variables from a variable library inside a pipeline.
Current state is when we add a variable from a library variable, we can only add once at a time.
If we have 4 variables libraries to import with 10 variables inside, we need to repeat this option 40 times. It can lead to human misclick.
Second improvment : When we have added all those variables it looks a bit messy in the library variables pane with lot of variables (1variable = 1 line). Maybe we can group them by variables libraries there ? Or find a way to make it more visual ?
Context:
I'm having a pipeline orchestrator, which is runing another pipeline 4 times to ingest data from 4 different datasources. The 4 uses the exact same pipeline, only changing the parameters with the library variables. I have 10 parameters for each libraries, which lead me to import 40 variables in the orchestrator to make it work. Tomorrow, I can add new sources again, and it would increase everytime by 10 the number of variables from libraries I need to import. Hence the difficulty with managing so many variables from the current library variables pane.
Thanks for reading!
2 Comments
- frithjof_vCommunity ChampionCurrent workaround for adding multiple at one time is to use the Edit JSON of the data pipeline
Recent ideas
Reintroduce Tenant/Capacity Switch to Control "Users can create Plan items" Post-GA
During the Preview phase of Fabric Plan items, administrators had access to a dedicated tenant/capacity setting: "Users can create Plan items". With General Availability (GA), this granular administr...Sri-Surendra_Ku47 minutes agoNew MemberNew78Views9likes1CommentSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull222 hours agoAdvocate INew4Views0likes0CommentsImprove Relationship UI Wording to Better Reflect Filter Propagation Direction
The current relationship dialog can be confusing because the UI labels "From" and "To" do not always align with users' linguistic expectations regarding filter propagation. As per document : Relation...v-varunvv3 hours agoMicrosoft EmployeeNew13Views4likes0CommentsDynamic ADLS-Gen2 path input for Spark Jobs Main definition file
I would like the ability to add a dynamic input box on a spark job definition's "Main Definition File" "ADLS-Gen2 path". this would be useful to set base and variable paths across all spark jobs...mfink_db3 hours agoNew MemberNew223Views2likes1Comment