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
Access Variable Library in Semantic Models
Enable the Variable Library as a centralized location for storing all environment‑specific variables, allowing us to adjust them for promotion scenarios (e.g., from dev to prod) without relying on de...FreddyH18 minutes agoAdvocate IINew907Views31likes2CommentsEnhance Fabric Pipeline Monitoring with Parent-Child Pipeline Lineage and Parameter Visibility
Currently, Microsoft Fabric Pipeline monitoring lacks several capabilities that are available in Azure Data Factory, making troubleshooting and operational support challenging in enterprise environme...dwramreddy53 minutes agoRegular VisitorNew1View0likes0CommentsDynamic 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_db5 hours agoNew MemberNew238Views2likes2CommentsReintroduce 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_Ku8 hours agoNew MemberNew106Views14likes1Comment