Is it possible to update Power Platform Dataflow parameters dynamically before refresh?

(0) Share

Report

Posted on by CU26061755-1

Title: Is it possible to update Power Platform Dataflow parameters dynamically before refresh?

Hi everyone,

I'm using Power Platform Dataflows (Dataverse) and have a dataflow with a parameter (for example, a SharePoint Site URL or file path).

My goal is to update the parameter value dynamically before triggering the dataflow refresh, ideally from Power Automate or through a REST API, so that each refresh can use a different value.

I've looked into:

Power Automate's Refresh Dataflow action, but it doesn't seem to allow passing parameter values.
The Dataverse msdyn_dataflow table and Web API.
Various undocumented PATCH endpoints mentioned online, but I couldn't find any official Microsoft documentation confirming they are supported.

My questions are:

Is there any officially supported way to update a Power Platform Dataflow parameter at runtime?
Can a parameter value be read dynamically from a Dataverse table during refresh without manually editing the dataflow?
Has anyone successfully updated dataflow parameters using the Dataverse Web API or another supported API?
If this isn't supported, what is the recommended architecture for dynamically changing a SharePoint site URL or file path before refreshing a dataflow?

I'm referring specifically to Power Platform Dataflows (Dataverse), not Fabric Dataflow Gen2.

Any guidance or working examples would be greatly appreciated.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

sannavajjala87 515 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

There’s no official way to pass or override parameter values at refresh time (Power Automate can only trigger the refresh). Updating parameters via Dataverse (msdyn_dataflow) or REST API isn’t supported in a reliable/official way. Dataflows expect static configuration, so dynamic source switching (like changing URL/path per run) isn’t natively supported.

Keep the dataflow static and move the “dynamic” logic outside (e.g., Power Automate writes to a staging table/file, and the dataflow always reads from that).

Or maintain multiple dataflows and control which one runs.

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
For Power Platform Dataflows (Dataverse), the most robust and supported approach is to avoid relying on editable dataflow parameters. Instead, externalize the

variable values into a Dataverse configuration table (or another supported data source) and have your Power Query read those values during execution. Your

process would then be:

Update the configuration record (using Power Automate or the Dataverse Web API).

Trigger the dataflow refresh.

The dataflow reads the latest configuration and imports data from the appropriate SharePoint site or file.

This pattern is fully supported, easier to maintain, and avoids depending on undocumented APIs or unsupported runtime parameter updates.

Was this reply helpful? Yes No