Retain Subscription When Moving Reports to Different Workspaces

[c_schrotberger]

Hello!  We are in the process of tying our PowerBI workspaces to Azure DevOps (ADO) for version and release control.  For example, we currently have a workspace called "Retail" and are making "Retail Dev" and "Retail Test" and using the existing one as Prod.  When we use ADO to copy the workspace to a repo to republish to Dev, Test, then back to prod (so they are all in sync), we lose any subscriptions that are set up on the production reports.  Is there any way to retain the subscription information, if so how?  If not, is there a way we can use an API to re-set up the subscriptions?  We did find the current APIs to pull down current subscription information.  

[v-hjannapu]

Hi @c_schrotberger,

I would also take a moment to thank @tayloramy, @cengizhanarslan  for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Regards,
Community Support Team.

[tayloramy]

Hi @c_schrotberger, 

There is no way that I know of to do this. 

You might be able to use the APIs to get a list of subscriptions, and then re-create them on the new artifact, but there's no easy "move this report to another workspace with subscriptions" button. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[cengizhanarslan · Accepted solution]

Subscriptions are tied to the report artifact in a specific workspace (and often the user + report ID). When you republish/recreate the report via ADO deployment, you’re effectively creating a new report object, so the old subscription objects don’t “follow” it. There isn’t a built-in way today to automatically retain them through redeployments.

If you want to avoid losing them, don’t replace the report in Prod. Instead keep the same report item and only update the dataset/model behind it.