📝 Description: In Microsoft Fabric Data Pipelines, the Switch activity requires a mandatory default branch, even when all valid cases are explicitly defined and handled. This limits flexibility and leads to unnecessary clutter or workarounds in pipeline design. 💡 Feature Request: Please add support for optional removal or disabling of the default branch in the Switch activity. 🔍 Why This Matters: 🔄 Cleaner Logic: In many scenarios, all possible input cases are explicitly handled (e.g., "csv", "json", "parquet"), and a default branch serves no meaningful purpose. 🛠️ Developer Control: Sometimes, it’s preferable to fail or stop execution if no case matches, rather than route execution through a forced dummy path. 🧼 Improved UX: The current behavior leads to unused or “empty” default branches, which clutters the pipeline canvas and adds confusion during maintenance. 📊 Consistency: Programming languages and orchestration tools often allow Switch/Case logic without requiring a default block. Aligning with this flexibility would be consistent and intuitive. ✅ Suggested Implementation: Add a toggle to disable the default path. Alternatively, provide an "on no match: terminate/error/continue" option. 🚀 Impact: This small change would: Simplify complex pipelines Improve usability Empower developers with more control over flow logic
... View more