Deploy button disabled trying to deploy to previous stage

[m-colbert]

HI All,

I've been working through a tenant implementing pipelines. I start by deploying artifacts backwards from Production to Dev-Test stage. Been working through a dozen or more pipelines. The one I'm working on will not enable the deploy button. 

The Dev-Test stage is empty, all items are selected from Production stage, 113 in total. Originally the Dev-Test stage workspace was set to Large Dataset Storage format where production was small. That has been adjusted to be in synch.

I went back to the old UI and it allowed me to select Deploy to previous stage. Presented the dialog where I entered my note and then received this error.

Any ideas on what else to check is greatly appreciated.

[v-sshirivolu]

Hi @m-colbert,
Thanks for reaching out to the Microsoft fabric community forum.

If the “Deploy to previous stage” button is unavailable, please verify that the Dev-Test stage has an assigned workspace and that it is completely empty there should be no reports or datasets present. Additionally, ensure that both the Production and Dev-Test workspaces have identical settings, particularly regarding storage format. You must also have at least Contributor access in both stages for deployment to proceed.Since the previous UI allowed you to attempt deployment but resulted in an error, this may indicate a settings mismatch or a background issue. To resolve this, consider removing the Dev-Test workspace from the pipeline and re-adding it to refresh the configuration. Alternatively, you can test with a new workspace to determine if the problem is specific to the current one. If the issue persists, you may manually export reports from Production and import them into Dev-Test as a workaround.

 
Go through the below Microsoft documentation for your reference :
Fabric Application lifecycle management (ALM) deployment pipelines deploy content - Microsoft Fabric...

If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it

Best Regards,
Sreeteja.
Community Support Team

[pankajnamekar25]

Hello @m-colbert 

Possible issue

The Deploy button is disabled when trying to move artifacts from Production to Dev-Test, and using the old UI leads to an error despite both workspaces being synced.

Solution

 Ensure both workspaces have identical storage settings, capacities, and permissions; if the issue persists, remove and re-add the Dev-Test stage or contact Microsoft support with the Activity ID for backend diagnostics.

Thanks

 Pankaj Namekar | LinkedIn

If this solution helps, please accept it and give a kudos (Like), it would be greatly appreciated.

[m-colbert · Accepted solution]

Hi @pankajnamekar25 

Thanks for the response, but I checked all of the standard conditions. I did open a ticket with MS since I noticed in the old pipeline UI it had more items that the new UI. What we found is that there are ghost references from a couple dashboards that were deleted over 2 years ago.
When trying to deploy, it can't find these dashboards, so it fails. And since going backwards from prod to dev-test is all or nothing, its a showstopper. Even though the continue if 1 or more items fail option is checked, not sure that even works. 
So at this point, we are waiting to see if there is some way they can delete these old references from our workspace, otherwise I will need to get creative. 
Thanks again for the response.