cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Solution failed to import: Solution Upgrade action failed after import as holding. InnerException is: Solution dependencies exist, cannot uninstall.

Hi,

 

I'm trying to understand how to import an updated solution, but I tend to run into this same error with different projects.

 

Initially, I imported my solution from my dev environment to my prod environment as a managed solution. Then, I modified my dev solution, which includes removing an environment variable that is no longer necessary. When I try to import this updated solution into prod, I choose the Upgrade option:

Jsalaz1989_0-1636977952410.png

This option explicitly states that "any objects not present in the newest solution will be deleted". Yes, that is precisely what I'm hoping for, I don't want to see that old environment variable in prod, since it is no longer necessary.

 

However, when I try to upgrade, I get this error:

Jsalaz1989_1-1636978116517.png

 

As far as I understand, it's complaining that "Solution dependencies exist, cannot uninstall." and specifically mentions a certain EnvironmentVariableDefinition. But isn't that exactly what Upgrade claimed to do? I know that variable currently exists, the whole point is to detect that it exists in prod but not in dev and therefore get rid of it.

 

You can also see that it creates a new solution, tacking on "_Upgrade" to the name, instead of replacing the old one.

 

This has happened often with other solutions so in prod I just end up erasing the old solution and importing the new one as if it were the first time prod ever sees this solution. However, this doesn't feel right. There is either something I'm misunderstanding about the Upgrade option, or something is not working right on Microsoft's side. Maybe I should always be using Update instead, idk, but it's not clear by the import wizard.

 

Also, in time I would like to automate this headache-y and manual devops flow I currently use (there are other issues or quirks that arise when doing this manually it seems). Perhaps when I do get some ALM going, then this error will no longer appear, but for now I would really like to understand what's happening as I step through this manually.

 

Thanks

10 REPLIES 10
Nievechica24
Frequent Visitor

I am getting the exact same error. Am I importing the solution incorrectly or is this a known issue?

mikael_andersen
Frequent Visitor

@Anonymous Running into the same issue however for us it's dropping a column.

 

Did you find a solution or are we left with deleting the solution first - that seems very wrong to me.

 

As a side note we have ALM up and running, but that makes not difference. Actually fails more often than manually exporting and importing.

I have not found a better workaround than deleting the prod solution and re-importing it. I agree that it seems quite wrong.
And of course we get no input from Microsoft here. I've even tried contacting our company's MS support people directly and they just ignored me. And that Tata Consultancy group they use was copied as well, but nobody replied.

Having the same problem today. Anyone know a workaround? 

Daved5
Advocate I
Advocate I

I am having the same problem.  I am nervous to delete the Solution in Production.  I assume, that this will not delete the tables that are part of the solution ?  Can someone confirm that i will not lose the data in the tables of the solution in production ?

mikael_andersen
Frequent Visitor

@Daved5 You should be nervous. If you uninstall/delete the solution that data will be lost, so in most cases is not an option. See this link https://learn.microsoft.com/en-us/power-platform/alm/maintain-managed-solutions where they state below:

mikael_andersen_0-1664788585980.png

 

Nievechica24
Frequent Visitor

After working with Microsoft Support, they had us delete the existing solution, go into the solution called "Default Solution" within that environment, delete all of the connection references and custom connector connections we had and then re-import. It worked for us after that. Not sure if this would help you.

mikael_andersen
Frequent Visitor

We also engaged with Microsoft support and they ended up running some scripts to delete attribute maps that caused some kind of circular dependency. Below is what they wrote as a hint to avoid it in the future.

 

--- From Microsoft support ----

Cause:

An attribute mapping was present in source and target both as unmanaged / as part of the active layer; expectation was that in target the component is managed. And since we cannot delete the attribute mappings directly from UI, the only way found to delete it from target was through a script mitigation.

 

Mitigation:

Run custom mitigation scripts to: delete the entity map for the 2 entities, delete the 2 entity relationships and then proceed with deleting the lookup attribute.

 

Note:

In order to avoid this from happening in the future we recommend to refrain from creating/importing unmanaged attribute mappings in target (in a managed environment). What we saw was a very particular situation where an attribute mapping was present in source and target both as unmanaged / as part of the active layer; expectation was that in target the component is managed. And since we cannot delete the attribute mappings directly from UI, the only was found to delete it from target was the above method – script mitigation.

 

-----

 

Hope this can help others in a similar situation.

mikael_andersen
Frequent Visitor

We also engaged with Microsoft support and they ended up running some scripts to delete attribute maps that caused some kind of circular dependency. Below is what they wrote as a hint to avoid it in the future.

 

--- From Microsoft support ----

Cause:

An attribute mapping was present in source and target both as unmanaged / as part of the active layer; expectation was that in target the component is managed. And since we cannot delete the attribute mappings directly from UI, the only way found to delete it from target was through a script mitigation.

 

Mitigation:

Run custom mitigation scripts to: delete the entity map for the 2 entities, delete the 2 entity relationships and then proceed with deleting the lookup attribute.

 

Note:

In order to avoid this from happening in the future we recommend to refrain from creating/importing unmanaged attribute mappings in target (in a managed environment). What we saw was a very particular situation where an attribute mapping was present in source and target both as unmanaged / as part of the active layer; expectation was that in target the component is managed. And since we cannot delete the attribute mappings directly from UI, the only was found to delete it from target was the above method – script mitigation.

 

-----

 

Hope this can help others in a similar situation.

ADPerkin
Frequent Visitor

Just had exact same issue - interestingly for us importing with Replace rather then the default Upgrade option works. When we try Upgrade, we also get a partly imported solution left behind, which has to be manually deleted before you can attempt a re-import.

Our issue definitely related to Power Automate, and connection references like Nievachica24 whereas it looks like Mikael's issue related to table lookups.

My suspicion was an unmanaged solution layer. I checked all objects referred to in the solution and it was an unmanaged layer on one of the flows. Deleted it and solution imported fine.

I really dont like the way that some elements remain editable in managed solutions, (This is a very old issue from Dynamics on-prem) particulary workflows and flows. It should always be a solution migration process that updates the target.

Hope that helps someone.



Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,173)