Forum Discussion
Promoting reports from Test to Production not finding right dataflow
Did you remove anything or publish over the top? If you've removed and the published new, that could be the issue.
For one of the 2 reports we have seen the issue for, we did have to remove the report and dataset in test, because the Exploratory/Dev -> Test deployment was also not going through properly. As a result when deployed to production it was coming through as a new report which makes sense. The test deployment was finding the test dataflow though, but the production deployment didnt find the production dataflow.
For the second we had no issues deploying to Test, but still when deploy to production (overwriting the previous version), it remained connected to the test dataflows rather than production.
The dataflows havent been removed at any point
I'm not sure I follow exactly but when I've found myself in this scenario, I would remove entirely and push it through from dev all the way through.
We've done both before with no issues, promoting as a new report and uprevving existing versions in the target workspace via deployment. It's only in the last week we've had this issue though.
The preference for promoting over the top of the existing version where possible is to maintain the web address to the report mostly.