Once a managed package is released, its components are locked. To remove a component — for example, to eliminate deprecated functionality or resolve compatibility issues — partners must either use the Delete Managed Components feature or request that Support revert the package version to beta
1. Partners may request to enable the feature to Delete Components in Managed Packages in their packaging org by logging a case in the Partner Community. For details, see How to Create a Partner Community Salesforce Account in order to log a case.
Note: Although a component is deleted, its Name remains within Salesforce. You can never create another component with the same name. The Deleted Package Components page lists which names can no longer be used.
Also, some Components Available in Managed Packages are not developer-deletable.
If a component can't be deleted using this method, you'll need to follow option 2.
2. Support can change the release version from Managed-Released, to Managed-Beta if certain conditions are met. Be sure to provide support with the following details:
i. Package Version details - Name, version, etc.
ii. Package version in question and later versions should not be currently installed in any subscriber org (if installed, they need to be uninstalled)
iii. If the package version in question and later versions have patch org created. If you do have any patch org created, please mention that in your case and confirm if it is ok to purge the patch org. (Patch org needs to be purged to revert the package)
Note: We can't change a managed package to an unmanaged package.
Delete Components from Managed Packages
Reverting a Managed-Released package version back to Beta
Salesforce Support YouTube video: Step-by-step walkthrough of how to delete a component from a 1GP managed package using the Delete Managed Components feature
How to Delete a Component from a Managed Package
000385399

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.