First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Behavior of Specific Metadata in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Plan the Release of First-Generation Managed Packages
Remove Components from First-Generation Managed Packages
Delete Components from First-Generation Managed Packages
Modifying Custom Fields after a Package Is Released
Manage Versions of First-Generation Managed Packages
View Unused Components in a Managed Package
Push Package Upgrades to Subscribers
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Modifying Custom Fields after a Package Is Released

The following changes are allowed to custom fields in a package, after it’s released.
Available in: Developer Edition

  • The length of a text field can be increased or decreased.
  • The number of digits to the left or right of the decimal point in a number field can be increased or decreased.
  • A required field can be made non-required and vice versa. If a default value was required for a field, that restriction can be removed and vice versa.