Forum Discussion

FireFighter1017's avatar
FireFighter1017
Icon for Advocate III rankAdvocate III
1 year ago

Dataflow query in desktop do not obey parameters set values

I got a dataflow that we have published in a workspace that is part of a deployment pipeline (DEV-QA-PROD). I have defined parameters to allow changing the workspace Id and dataflow Id in Power BI S...
Need Help
Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi FireFighter1017 ,

Thanks for reaching out to the Microsoft fabric community forum.

 

This issue occurs because Power BI deployment pipelines automatically override dataset parameters according to the rules set in the environment configuration.

Therefore, even if you update the parameter in Power BI Desktop or manually republish with DEV/QA values,

the deployment pipeline will still replace the parameter values with those configured for the current environment, which in your case seems to be PROD.

Review and Update Deployment Pipeline Parameter Rules

In Power BI Service, go to the deployment pipeline containing your dataset.
Navigate to the relevant environment (such as QA or DEV).
In Deployment Settings, check the Parameter rules.
You may find parameters like WS_WORKSPACE_NAME and DF_DATAFLOW_NAME set to PROD values.
Update them to the correct DEV/QA values for that environment and save your changes.

Disable Parameter Override (Optional)

If you want to prevent deployment pipelines from overriding your parameters, uncheck "Override during deployment" for each parameter in Deployment Settings.

However, it is generally recommended to configure parameters correctly for each environment rather than disabling overrides.

Additional Validation

To test in Power BI Desktop, set the parameter to a QA/DEV value and verify that the query editor preview uses the correct data source. After publishing to a specific workspace, check the parameter values in the dataset settings. If using a pipeline, ensure it is not overriding these values during deployment.

Following these steps will help make sure your workspace and dataflow IDs are set correctly for each environment and that parameters work as intended.

If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it

Best Regards,
Sreeteja.
Community Support Team 

 

 

FireFighter1017's avatar
FireFighter1017
Icon for Advocate III rankAdvocate III
1 year ago

Anonymous ,

 

Also, DEV can't have deployment rules.  Even though I change the parameter values in the Datset settings in Power BI Service for DEV, it still reads data from PROD.  I also tested if the workspace parameter has QA's GUI and the dataflow has DEV GUI, it still returns data from PROD.

 

As I mentionned, the biggest issue is that we did your "Extra validation" and we have this behavior in Power BI Desktop.

 

Because we are using Git Integration with Github, we save our reports as PBIP.  So when I open the report in Desktop mode, I do it from the local repository.

The report in Power BI Service DEV is updated through Git integration from Github.

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    Hi FireFighter1017 ,

    Thanks for reaching out to the Microsoft fabric community forum.

    Power BI Desktop may cache previous connection info from the PowerPlatform.Dataflows() connector, so even if you update parameters, it might still use old PROD details from connections.json. This can make parameter changes seem ineffective.

    Try These steps:

    1. Clear Data Source Settings in Desktop:
    Go to File - Options and Settings - Data Source Settings.
    Clear permissions for Power Platform and remove cached connections.

    2. Inspect PBIP Files in Git:
    Check parameters.json – confirm the right values are set.
    Check connections.json – this may have hardcoded workspace/dataflow IDs that override parameters.

    3. Regenerate PBIP Cleanly:
    Try opening a clean .pbix (not from PBIP), and test parameters for DEV.
    Once confirmed working, export it as PBIP again.
    Compare the new connections.json with your repo version.

    4. Consider Switching to OData.Feed():
    Instead of using PowerPlatform.Dataflows(), try:

    let
    url = "https://api.powerbi.com/powerbi/globaldataflows/v1.0/myorg/groups/" & WS_WORKSPACE_NAME & "/dataflows/" & DF_DATAFLOW_NAME,
    data = OData.Feed(url)
    in
    data

    This gives full control over the connection URI and respects parameters reliably.


    The issue is most likely caused by how PowerPlatform.Dataflows() behaves in PBIP projects it's not always reactive to parameter changes due to caching and metadata binding. Using OData.Feed() or cleaning out connections.json may help regain control.

    If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it

    Best Regards,
    Sreeteja.
    Community Support Team 

    • Anonymous's avatar
      Anonymous
      Not applicable
      1 year ago

      Hi FireFighter1017  , 

      Just wanted to check if you had the opportunity to review the suggestion provided?

      If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it.

      • FireFighter1017's avatar
        FireFighter1017
        Icon for Advocate III rankAdvocate III
        1 year ago

        Hello Anonymous ,

        I'm currently reviewing your suggestions.

        I'll let you know once I've gone through.