Unanswered

Importing solution fails as it requires the "Active" solution - Urgent

(1) Share

Report

Posted on by lachiee

Hi guys,

I am trying to import my solution from dev environment to production. Previously, I didn't have any problem with this action, but now I get the following error:

I assume, this "Active" solution must be some internal solution, as I couldn't find it in any of my environments.

Additional info: this solution requires integration with Business Central, however, I solved these dependency issues (it requires then the solutions "MicrosoftDynamicsNavIntegration" and "bcbi_CdsBaseIntegration", which are already there).
Furthermore, the solution includes the Dynamics Customer Service Hub as well.

Edit: by testing it with a dummy solution, I face the same error if the Dynamics Customer Service Hub is included in the solution, but without that app, it works.

Thank you for any input! It is kind of urgent now!:)
Have a great day,
Laci

Categories:

Governance & administering

All responses (6)

Answers (0)

Sort by

Ben Thompson 1,400 on at

Like
a
(5)

Report
Copy link

Link copied!

Scrub that previous post. There is an issue in the Import routine of Make.powerapps.com which shows that you have an error with the Active Solution without telling you what the actual issue is - which is likely to be a missing dependency in your solution.

To identify the issue - you need to start off at the old All solutions page in the advanced settings so orgxxx.crmyy.dynamics.com/main.aspx?settingsonly=true and kick off the import from there. That will bring up the actual issue in a way that can be fixed.
lachiee 20 on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks for the tip!

Unfortunately, I got there the same message, but in different formulation, i.e. "The following components are missing in your system and are not included in the solution. Import the managed solutions that contain these components (Active) and then try importing this solution again."

I found another thread with this message, but there was no real solution found.
Ben Thompson 1,400 on at

Like
a
(1)

Report
Copy link

Link copied!

As I said before the way to identify the issue is to use the old solution import routine within Dynamics 365 advanced settings - I did that yesterday to resolve the issue we had importing a solution.
Ben Thompson 1,400 on at

Like
a
(1)

Report
Copy link

Link copied!

Given that I'm seeing other people with the same problem I've added a blogpost about it at https://www.processpower.dev/how-to-install-a-powerapp-solution-when-the-active-solution-is-missing/
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

I had this issue with a solution that contained only Power Automate flows. To solve this I exported the solution from the Classic interface. This then told me that there were missing dependencies in the solution and what they were, it also told me that I could add the dependencies in the solution by editing the solution (in Classic mode) and using the "Add required components" button
I did this for each Flow in the solution, saved the solution then exported it, there were no issues on the export. I then imported into another environment successfully.

regards
Terry

---
please mark as solution if this has met your requirements
MuhannedNidal 6 on at

Like
a
(1)

Report
Copy link

Link copied!

Try this way.

https://d365demystified.com/2020/10/14/there-are-missing-dependencies-install-the-following-solutions-before-installing-this-one-active-connection-references-missing-in-power-platform-solution/