Forum Discussion
Deployment Pipeline/Parameter Issues
Hi, cainr6
You first need to make sure that you configure the correct parameters in the Power BI service, according to your description, the data pulled into the test report is wrong, then you should check the parameter settings associated with it. You can refer to the following official documentation to check if there are any configuration errors:
Pipeline parameters and variables - Azure Data Factory & Azure Synapse | Microsoft Learn
The data is not copied during the deployment, only the metadata, so a refresh is required to pull the latest data based on the configured parameters, you can try manually refreshing the semantic model to see if you can get the correct data.
In addition, if you are using a deployment rule for your parameters, it is recommended that you check that your rule is configured correctly, and you can click on the link below to learn how to deploy the rule:
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for the response - all of this is configured correctly. There are rules established to promote to the next environment using the parameters.
Like i mentioned, i can change the paramter setting in the service back to the dev environment and refresh and still receive the same values in the dataset.
Hi, cainr6
Thank you very much for your reply. If you're all configured correctly, and you want to know what happened to the original report, you may need to resort to a different tool. For example, I connect to a SQL Server database and this problem occurs. Then I'll use the SQL Server Profiler in SSMS to track down if there are any errors in the queries that are being made by the current Power BI Service to the data source.
If we find an error in the query statement, then we can check if the measure or other settings in our report are correct.
If you mentioned at the beginning that you can deploy another version of the semantic model and that it gets the right data, then you need to check that the two semantic model configuration steps are exactly the same to make sure that nothing is missed.Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi cainr6 ,
After deploying the reports from one env to other refresh your semantic models and go to your report and refresh your visuals.After doing the deployment wait for 2-3 min's .If the issue is not resolved recreate rules on each stage and try again or you can create a new pipeline by deleting the existing one.I have faced the similar issue when I'm showing demo to our users.
Thanks,
Sai Teja
