Problem Statement: Currently, the Pipeline Expression Builder in Microsoft Fabric Data Pipelines does not support any form of inline comments. Expressions like @concat('*','_',pipeline().parameters.pFileDate_YYYYMMDD,'.txt') have no way to carry documentation or intent alongside them. Any attempt to add //, #, or /* */ style comments causes expression validation to fail. Why This Matters: Data pipelines in production environments are built and maintained by teams. Complex expressions — especially those involving dynamic file patterns, conditional logic, or chained functions — are difficult to understand at a glance without context. Without native comment support, teams are forced into workarounds like: Adding dummy Set Variable activities as visual labels Writing intent in the activity Description field (not visible during expression editing) Maintaining separate documentation outside the pipeline These workarounds are fragile, easy to forget, and do not scale well across large pipelines. Proposed Solution: Allow comments inside the Pipeline Expression Builder using a clearly defined syntax. For example: @concat(
'*', /* wildcard prefix */
'_',
pipeline().parameters.pFileDate_YYYYMMDD, /* injected date: YYYYMMDD */
'.txt'
) Or alternatively, a dedicated Notes / Comment field scoped to each expression (not just the activity Description) that is visible while authoring the expression. Expected Benefit: Improved readability and maintainability of complex pipeline expressions Reduced onboarding time for new team members Better self-documentation of pipelines without needing external tools Brings pipeline expression authoring closer to the standard expected in modern developer tooling Category: Data Factory / Fabric Data Pipelines / Pipelines
... View more