Forum Discussion
Super UserPipeline copy/move from Prod to development
Hi,
On the power bi service, we have dataflow, dataset, reports, paginated reports, files and more all in prod, and it is premium workspace from the beginning. Now, we enabled pipelines, don't ask me why now and not before (clue: DBA)!
I am seeing steps and aware on how to move from dev to test to prod using pipeline.
Is there a way to move all from prod to dev?
Also, to keep this as a strategey to integrate back with the use of pipelines ?
TIA
-------------------------------------------------
Note: I can download each from prod and re-upload to dev by fixing all the guids. But want to see if there is a automatic or easier way. I have over 500 items.
you can back-port from Prod to ITG, and from ITG to DEV. I don't think you can back-port from Prod to DEV directly.
Don't know how many objects you're dealing with but would something like this work in order to maintain stuff in the production space...
1) Save out copies from existing dev/test spaces.
2) Publish everything that doesn't already exist in prod.
3) Wipe your dev and test spaces
4) Backfill to empty spaces from prod.
5) Publish "correct" dev versions into the dev workspace over the top.
I think that will at least protect guids for production.
11 Replies
- lbendlin
you can back-port from Prod to ITG, and from ITG to DEV. I don't think you can back-port from Prod to DEV directly.
sevenhillsThank you.
We are seeing only option as doing manually
- Download and upload each artifact, like fresh new reports from prod to dev
- For each one, fix the guid/links ...
- By doing this, we may lose our history of changes or refresh history.
- sdemei
Advocate I
Hi,
Is there a build in option to "Back-port"?
- bcdobbs
Community Champion
See the note on backward deployment here...
https://docs.microsoft.com/en-us/power-bi/create-reports/deployment-pipelines-get-started
The option is only available if prior workspaces are empty.
- sevenhills
Thank you, I read the link before and our dev workspace is not empty.
Like it got messy, because they opened both and we started doing in both prod and dev.
- bcdobbs
Don't know how many objects you're dealing with but would something like this work in order to maintain stuff in the production space...
1) Save out copies from existing dev/test spaces.
2) Publish everything that doesn't already exist in prod.
3) Wipe your dev and test spaces
4) Backfill to empty spaces from prod.
5) Publish "correct" dev versions into the dev workspace over the top.
I think that will at least protect guids for production.
sqaar__Helper I
Even tho, I did "Reversed deployment pipeline" to see if i could move all things to the next stage (from prod to dev, then remove the pipeline and move from dev to prod) and its exactly the same error, no matter if i try to move all of them, one by one, for reports, datamart, and datasets.
Patryk