Forum Discussion
Promoting reports from Test to Production not finding right dataflow
Up until last week, when we promoted a report from test to production, it found the production version of the input dataflows automatically and connected up to those.
Last week though we noticed for 2 reports, that they maintained their connections to the test dataflows instead.
Has something changed or does anyone have any suggestions for why this approach might suddenly have stopped working?
Thank you!
6 Replies
- AnonymousNot applicable
Since it stopped working, were there any changes in either the dataset or the dataflow in question?
- davidperry2Frequent Visitor
There havent been any changes to the dataflow(s), we have made changes in the report and dataset which is what we are deploying, but nothing significantly different to before and we've never previously had issues with it automatically finding the production dataflow upon deployment.
I don't know if it's just a coincindence but it's the first deployments we were doing since all datasets seem to have been renamed semantic models.- AnonymousNot applicable
Did you remove anything or publish over the top? If you've removed and the published new, that could be the issue.
- davidperry2Frequent Visitor
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