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
Bulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal1401973 hours agoFrequent VisitorNew3Views0likes0CommentsAbout "Download SQL database project" and fix the downloaded project
1. The sqlproj must be fixed, it is downloaded without the xml markup line <?xml version="1.0" encoding="utf-8"> 2. The sdk must be updated: Actual: <Sdk Name="Microsoft.Build.Sql" Version="0.1...Jarrinf12 hours agoFrequent VisitorNew48Views3likes2CommentsEventstream MQTT broker source: V3.1.1 support
The Eventstream MQTT broker source supports connections with public MQTT brokers that offer MQTT V5 support. Please offer support for V3.1.1 too, because this is still a valid and widely used ver...svelde14 hours agoSuper UserCompleted1.4KViews6likes4Comments