Import failed due missing dependencies (deleted connection reference)

(0) Share

Report

Posted on by SkiDK

1,016

Hi all,

I have a solution with an app and connection references I try to import to another environment through a pipeline. It fails because it has a missing dependency: a SQL connection reference.

Thing is that this solution was cloned from another solution in which the missing connection reference was created and thus cloned. I then deleted the connection reference from the cloned solution, but now I cannot import this solution to another environment due this missing dependency.

Is there a way I can remove this dependency of the removed connection reference in the solution?

Many thanks!

Ski

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Ram Prakash Duraisamy 5,593 Super User 2025 Season 2 on at

Like (1)

Report

Hello @SkiDK,

Can you please click Download Log File and share me the same to provide solution from my end.

Click Gear Icon at the top
then Click Advance settings then Click Solutions
Try Importing there and Download the log file and share the same to proceed further

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

Was this reply helpful? Yes No
Verified answer

SkiDK 1,016 on at

Like (3)

Report
Hi @rampprakash, thanks for your reply, but I found the solution. See below:

Export solution, and open zip file
Removed all objects linked to the missing connection reference in 'customizations.xml'
Removed missing dependency between <MissingDependencies> tags for missing connection reference in 'solution.xml'
Zip the folder with changes to files
Import in same environment to update old solution
This method also works if you cannot delete certain unused items due dependencies. After doing this, you can open the solution and delete the unused items.

Was this reply helpful? Yes No
Ukiman1014 on at

Like (0)

Report

Following these steps allowed me to get past the initial check, but during the import it still failed due to the same issue, but just for one of the connections. The thing that's the most frustrating is it's not used anywhere in the solution.

Was this reply helpful? Yes No