Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hi community,
Think I've found a rather random bug when passing a Pipeline parameter to Dataflow parameter, (and the error message is useless).
I have managed to figure out and resolve but thought I'd share.
Pipeline parameter Name: DestinationName, default value: DestinationName
Dataflow parameter Name: DestinationName
Basically, if the paramter name and value are the same it fails... I've changed the value to TableName and the pipeline works as expected. This is used for the Data Destination table name
Hi @CptDarling
Thanks for reaching out to the Microsoft fabric community forum.
Thanks for sharing this @CptDarling,
Really appreciate you taking the time to document this issue and the workaround. These kinds of quirks can be tough to track down, and your post will help others avoid the same frustration. Great catch on the parameter name/value conflict this insight is super helpful for anyone integrating Pipelines and Dataflows in Fabric.
Thanks again!
I would recommend submitting this scenario as a feature request in the official Power BI Ideas forum.
The Product Team actively reviews suggestions there, and if others in the community upvote it, it may be considered for future updates.
https://ideas.fabric.microsoft.com/
Best Regards,
Lakshmi Narayana
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
79 | |
46 | |
17 | |
11 | |
7 |
User | Count |
---|---|
82 | |
82 | |
27 | |
8 | |
7 |