web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Removing a field from a form within a patch and deploying to target environment

(0) ShareShare
ReportReport
Posted on by 22

I recently created a new patch where I removed a field from the main form of one of my custom entities. I didn't delete it from the entity because I want to retain any old data on the target environment, just removed it from the form. 

The patch was deployed onto another environment where the same field still existed on the form on the base solution. 

I expected the patch to update the same form on the target environment but it didn't, its still on the other form. What do I need to do in order to remove a field from a form on the target environment? 

I have the same question (0)
  • Suggested answer
    Bipin D365 Profile Picture
    28,983 Moderator on at

    Hi,

    Can you try increasing version number of the patch solution and deploy again.

    If this does not work, try creating normal solution instead of patch and add only form to that soluton then deploy.

    If found helpful, Please mark my answer verified.

  • Michael Kyle Profile Picture
    22 on at

    Hi, neither of those solutions worked for me unfortunately. The field still exists on target form.

  • Suggested answer
    Filipe Relvas Profile Picture
    on at

    Hi Michael,

    Forms, Sitemaps and OptionSets as you know are a bit different when compared with the remaining CRM Components.

    When you have multiple definitions i.e. solution / patch layers for these components the system will merge the definition.

    This means that if you have a Solution 1 with Form A and Field X and a Solution 2 with Form A without Field X the result from this merge will still contain Field X since another layer has it.

    I would suggest checking if you have any other solution that contains the affected Form and if not follow up with a Solution Upgrade for that solution. Solution Upgrade will Rollup any Patches you might have and the final result should be the one brought by the latest Patch assuming there are no other layers for that form.

    Documentation:

    - docs.microsoft.com/.../understand-managed-solutions-merged

    - docs.microsoft.com/.../create-patches-simplify-solution-updates

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 137 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 57

#3
Jimmy Passeti Profile Picture

Jimmy Passeti 50 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans