Forum Discussion
Dataflow Gen2 CI/CD activity drops parameter values on save.
Hi,
Thanks for your response. I've tried most of the suggestions, but unfortunately none of them worked.
However, I found one approach that does work:
- Pass the dynamic content into the dataflow parameters within the activity.
- Save the pipeline.
- Keep it open or, if you close, avoid opening the pipeline again, and execute it only through a schedule or a trigger.
I noticed that when you save the pipeline, the dynamic parameter values are preserved. The issue seems to occur when the pipeline is reopened in the workspace (or when it's executed directly from the pipeline page). At that point, the dynamic content appears to be overwritten.
As a workaround, every time you need to modify the pipeline (which requires opening it in the workspace), you'll need to reassign the dynamic content to the parameters before saving again.
In summary, keep the pipeline open while making your changes, then save it and execute it only through the scheduling or triggering mechanisms.
Hi,
Thanks for your response. I've tried most of the suggestions, but unfortunately none of them worked.
However, I found one approach that does work:
- Pass the dynamic content into the dataflow parameters within the activity.
- Save the pipeline.
- Keep it open or, if you close, avoid opening the pipeline again, and execute it only through a schedule or a trigger.
I noticed that when you save the pipeline, the dynamic parameter values are preserved. The issue seems to occur when the pipeline is reopened in the workspace (or when it's executed directly from the pipeline page). At that point, the dynamic content appears to be overwritten.
As a workaround, every time you need to modify the pipeline (which requires opening it in the workspace), you'll need to reassign the dynamic content to the parameters before saving again.
In summary, keep the pipeline open while making your changes, then save it and execute it only through the scheduling or triggering mechanisms.
Hey gabrielfagundes ,
Thanks for coming back and confirming what worked on your end — really appreciate you sharing the exact steps.
Your finding actually strengthens the theory that this is an authoring UI / rehydration issue rather than a runtime or parameter-discovery problem. The dynamic bindings clearly serialize correctly on save (schedule/trigger runs pick them up), but something in the reopen path is dropping or overwriting them before the next save.
For anyone else hitting this, the practical workaround is:
- Set the parameter values on the Dataflow Gen2 activity.
- Save the pipeline.
- Do not reopen or edit the pipeline unless necessary.
- Trigger runs only via a schedule or pipeline trigger — not from the pipeline authoring page.
- If you do have to reopen it, reassign the parameter bindings before saving again.
One suggestion: if you can, capture the pipeline JSON right after save and again after a reopen (before re-saving). That before/after diff is a very clean, reproducible case to attach to a Microsoft Support ticket — it makes it much easier for the product team to isolate the layer where the values are being dropped.
If my earlier reply helped point you toward the right area, please consider marking it as the Accepted Solution so others running into the same issue can find the thread faster.