Skip to main content

Notifications

Community site session details

Community site session details

Session Id : Js1yW1BbQzLFx/SEWRLplS
Power Apps - Microsoft Dataverse
Answered

Column in managed solution not being removed by upgrade

Like (1) ShareShare
ReportReport
Posted on 23 Sep 2024 14:09:50 by 606 Super User 2025 Season 1
Hi! I'm encountering behaviour of a managed solution that I didn't expect and I'm wondering if some of you have seen or resolved this before.
 
I've just started in a project where there is a dev and a prod environment. Both had an unmanaged solution installed. I've turned the solution in prod into a managed solution by
  • exporting the dev solution as managed,
  • removing the unmanaged solution in prod (which of course left the components in the environment) and
  • importing the managed solution in prod
The problem is, prod had an extra column in a table that isn't in the table in dev. I expected this column thus to be removed, so the solution in prod would be equal to dev. The extra column, however, remains. I've exported new versions and imported them, using the upgrade, stage for upgrade and update processes, but it's still there.
 
Thus, the question is: How can I remove a column in my managed solution in prod, now that importing a managed solution without the column does not work?
 
I've already tried cloning the solution in dev based on this article and staging for upgrade as described by this article.
  • NPPlatform Profile Picture
    606 Super User 2025 Season 1 on 24 Sep 2024 at 08:51:12
    Column in managed solution not being removed by upgrade
    Thanks for your response @FLMike .  The sentence "Because a managed solution will not remove unmanaged stuff from before or from another solution (managed or unmanaged)" explains my problem. So thanks! I'll have to dive into this more, because it seems that any columns that I now remove from the solution in dev still remain in prod, even though they have only been created after the whole change from unmanaged to managed. I wonder whether this is still a consequence of the components originating from an unmanaged solution. I'll test it further. Thanks for now!
  • Verified answer
    Michael E. Gernaey Profile Picture
    41,822 Super User 2025 Season 1 on 23 Sep 2024 at 17:16:22
    Column in managed solution not being removed by upgrade
    Hi,
     
    To me, this sounds like it was one of the items that got created in the Unmanaged layer, OR someone did it directly in prod, which created the unmanaged layer (additional).
     
    Either way, the only way to remove it is to manually go into the Default Solution and remove it.

    And before you do it, you can select that Column and look at Dependencies. Now if you removed the unmanaged solution and just forgot to delete this one change then you may not see the dependencies. But I suggest you check it first. Then manually delete it and publish all customizations.

    Because a managed solution will not remove unmanaged stuff from before or from another solution (managed or unmanaged)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Congratulations to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 146,786 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 66,093 Most Valuable Professional

Leaderboard

Featured topics

Loading started