Forum Discussion

sharathKumar's avatar
sharathKumar
New Member
10 months ago
Solved

Need Help: Making Dataflow Gen2 destination dynamic + syncing updated mashup.pq back to Fabric

Hi everyone,   I’ve built a Dataflow Gen2 pipeline in Fabric that connects to a Salesforce report using report id as the source and writes the data to a SharePoint folder as the destination.   Cu...
workspaces
  • sharathKumar's avatar
    sharathKumar
    9 months ago

    Thank you Vinodh247 for quick response. 

    I am thinking to build a notebook for SharePoint so that i can make it dynamic.

     

ANVS's avatar
ANVS
Advocate II
9 months ago

Hi sharathKumar 

Currently, Dataflow Gen2 doesn’t support dynamic destination paths or filenames (for example, parameterizing SharePoint site URL, folder path, or output file name). You can define parameters for source connections and query logic, but not for destination configuration — those settings must remain static.

Also, the Git integration in Fabric is one-way. Changes made in Fabric sync to Azure DevOps, but updates made directly in DevOps (like editing mashup.pq) don’t automatically sync back. The only supported method is to open the dataflow in Fabric, load the updated code manually, and click Save/Publish — this triggers a refresh of the dataflow definition.

Workarounds:

  1. Keep a static destination in Dataflow, and use a Fabric Pipeline or Power Automate step afterward to move or rename the generated file dynamically.

  2. Use parameters for other flexible items (like delimiter or site URL if you have multiple environments).

  3. If dynamic destination control is critical, use Fabric Pipelines or Azure Data Factory Copy Activity, which support fully parameterized sink paths.

In short — parameterizing destination paths isn’t yet supported, and reverse Git sync (DevOps → Fabric) isn’t available. Manual save or post-processing automation is the only workaround for now.

Please Like and Mark as "Accepted Solution" if you find it Useful.