Forum Discussion
Advocate IIDeployment pipeline based parameters for datasets reports and dataflows
mbbozzuto, the connection between the items will happen automtically after deployment. Learn more about it here- Deployment pipelines, the Power BI Application lifecycle management (ALM) tool, process - Power BI | Microsoft Docs
Hi mbbozzuto
It could be that per changes in the M query, the parameters won't be recognized.
As suggested above, using the deployment pipeline's parameters rule is probably be the preferable way here.
Microsoft EmployeeHi mbbozzuto
No configuration is needed. Just make sure that items are connected to eachother and both are on the same stage in different pipelines. for example:
Report on Dev stage in pipeline A is connected to dataset on Dev stage in pipeline B.
If that doesn't work for you so please open a support ticket since it's probably a bug we need to investigate.
As for adding parameter variables, it is possible to configure connections between dataset to dataset/dataflow using query parameters and then leverage parameters rules:
Deployment pipelines, the Power BI Application lifecycle management (ALM) tool, process - Power BI | Microsoft Docs
As for reports, please see here: Deployment pipelines, the Power BI Application lifecycle management (ALM) tool, process - Power BI | Microsoft Docs
BR,
Lee
Advocate IIThanks LeeBenjamin. We are deploying datasets to Power BI Service via the XMLA end point from Tabular Editor; the documentation (https://docs.microsoft.com/en-us/power-bi/connect-data/service-parameters) discusses modifying query parameters in the query editor of Power BI Desktop. Will the Power BI Service recognize parameters set via XMLA end point?
Currently, because we explicitly set the connection values in the M query for the Dataflows feeding the datasets, when we deploy the datasets between workspaces via pipeline, it retains the explicit connection values.