Deployment Pipeline/Parameter Issues

[cainr6]

I have a report that is managed in tiers of a deployment pipeline.

There are parameters controlling the data environment that the report is consuming and those parameters are configured in the service to promote the environment through dev, test, prod.

recently when deploying from dev to test and the only way i can explain it is that the data seems "stuck". The data pulling into the test report is wrong, but it is not coming from dev (or prod) and i have refreshed numerous times.

In testing this, i have republished to dev and redeployed to test. I have also changed the parameter in the service, refreshed, then changed it back. Even when i change the parameter to a different data environment and refresh the data stays the same.

I was able to redeploy another version of the dash and semantic model and the appropriate data is coming through but i am just trying to figure out what is going on with the other report, how it may have happened, and what i might be able to do to fix it.

Note: the test environment has shifted to a large data model so i cannot download the file from the test environment to review in power query.

[hackcrr]

Hi, @cainr6 

The Power BI service may be caching data. Clear the cache in the Power BI service to ensure that the latest data is loaded. You can go to Dataset Settings in the Power BI service and select the option to clear the cache.
Ensure that parameters are properly propagated through the deployment pipeline from development to test. You need to double-check that the parameters are configured correctly in the service for each environment and that the pipeline is lifting these settings correctly.
Verify that parameters are correctly bound to data sources and that parameter references are not problematic. You need to make sure that the parameters in the reports are correctly mapped to the appropriate data sources and that there are no syntax or referencing errors.
Check that the data sources in the test environment are correctly pointing to the expected databases. You need to check the data source settings in the test environment and ensure that it points to the correct database instance.
Ensure that there are no issues with stale data retained in the report or dataset. You need to perform a full refresh of the dataset to ensure that the refresh process completes successfully.
You need to validate the deployment pipeline rules and ensure that they are set to the correct lifting parameters and associated datasets.

If the problem persists, consider creating a new deployment pipeline and redeploying the report to see if you can resolve the issue

hackcrr

If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly

[Anonymous]

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:

Create deployment rules for Fabric's Application lifecycle management (ALM) - Microsoft Fabric | Mic...

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.

[cainr6]

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.

[SaiTejaTalasila]

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 

[Anonymous]

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.