Introduce shared / reusable schedule objects that can be referenced by multiple Fabric artifacts (multiple pipelines, notebooks, and other artifacts), similar to SQL Server Agent job schedules. This would allow teams to define execution timing once (for example, a nightly or hourly schedule) and apply it consistently across many workloads, rather than duplicating identical schedules per artifact. Shared schedules would reduce configuration drift, simplify maintenance, and make schedule changes safer and faster by allowing updates in one place. This capability would significantly improve enterprise operations, governance, and migration scenarios for organizations moving from SQL Server Agent–based architectures to Fabric, where coordinated execution timing across many processes is a common requirement.
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v10 hours agoCommunity ChampionNew615Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v18 hours agoCommunity ChampionNew17Views1like0CommentsBulk 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 ...vishal14019721 hours agoFrequent VisitorNew6Views0likes0Comments