Solution won't deploy to production from development

(0) Share

Report

Posted on by futr_vision

831 Moderator

I've gotten myself into a pickle. I've been working with Power Automate trying to get data from my Power App Dataverse tables into Azure Blob Storage. I had this working at one point but hit some issue. Long story short, I've been deleting and re-adding connections. Deleting and rebuilding flows. I thought I finally squared everything away in my dev environment because my flow was now working. Problem is when I go to deploy. It fails now. I get the following error.

The connectionreference(613ba08a-c326-4d8b-9e1d-460e5aa29284) component cannot be deleted because it is referenced by 2 other components. For a list of referenced components, use the RetrieveDependenciesForDeleteRequest.

Copilot(in Edge browser) basically gives me some C# to execute which is beyond my capabilities. Grok gives me directions to look for dependencies in the target environment but I can't find the references. I'm sort of stuck on what to do. My thought is backup my Dataverse tables from the production environment and just nuke the solution and then deploy from the development environment. Seems like that may be the fastest way to get my app updated. Any thoughts? It's a managed solution in production so I am limited on what I can do there.

Categories:

Error handling

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Gabriel G. 831 Super User 2025 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Why you want to delete the connection reference since it doesn't make any changes if not used. Anyway, you can reach the connection reference in your prod environment and check for dependencies directly on the component:

You will open a window showing dependencies categorized as 'Deletion blocked by' (and 2 other tabs). Note what is list there and make sure you remove your modify the connection reference in these components IN YOUR DEVELOPMENT ENVIRONMENT. Then, you package the changes and deploy to your Prod environment before retrying to deploy your first package and validate if you still have the error message.

I hope it helps!
_______________________________________________________________

Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.

Was this reply helpful? Yes No
futr_vision 831 Moderator on at

Like (1)

Report
Copy link

Link copied!

Thanks. Problem is that those dependencies don't exist in the development environment anymore. I think what I might do, because I haven't really made any major changes other than deleting connections and rebuilding flows multiple times, is to restore my development environment to the last time I was able to deploy to production and go from there. That should get me back to a point before I started screwing things up right?

Was this reply helpful? Yes No
Gabriel G. 831 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!

If you don't have much changes, it is a good idea. You still have your funky stuffs in Production, but you can fix it by deploy a solution to make the changes afte your restore. If you never had the ^problem in development and you got this in production, we probably missing something and it means Production environment is not align with dev environment, which is somekind of annoying :/.

You probably right and the restore should be a good thing :/.

Keep us informed!

Was this reply helpful? Yes No
futr_vision 831 Moderator on at

Like (0)

Report
Copy link

Link copied!

I think that is the best route. The only other issue I ever had were changes not getting pushed to production even though the deployment was successful (Yes. I did publish my changes in development). I had dozens of deployments without an issue and for some reason, on launch day no less, the changes were not deploying. I ended up nuking the production solution that time and redeploying the solution from development. Also had to restore a backup of the production environment to a sandbox environment in order to retrieve the tables since I forgot to back those up first. Good times. I'm not a PowerApps developer by trade. This is a side project, so I sometimes miss implementing best practices or am blind to some things. I appreciate the help and fast responses.

Was this reply helpful? Yes No
futr_vision 831 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hmm. A restore of the environment doesn't look like it restores connections. I might still be in the same boat. If I can't fix the connection issue I don't see any option other than backing up the tables in production and removing the solution from there and then deploying from development with all the new connections. Then I will need to restore production tables and I should be good to go. Thoughts?

Was this reply helpful? Yes No
Gabriel G. 831 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!

If you have changes that is not pushed in prod, have you checked for unmanaged layers on components in Production environment ? If you have an unmanaged layer, it will always be on top and hide the changes from your deployment.

To view unmanaged layers, you click on ‘…’ on a component and you click on ‘solution layers’. If the first on top is ‘default solution’, it is an unmanaged layer. You simply select it and click ‘delete layer’.

If you have 0 unmanaged layers, maybe xml files are corrupted and components are now stuck.

Was this reply helpful? Yes No