Overwrite Previous Package

The Overwrite Previous Package option gives Publishers the choice to Merge or Overwrite packages. The Merge/Overwrite choice is applied when a Subscriber installs a package.

The Overwrite Previous Package option is enabled by your Service Provider. The default single sign-on setting on on-premises installation is Off. The default single sign-on setting on the cloud is Off. (Contact Support to make changes.)

Considerations

• When the Overwrite Previous Package option is enabled, these options become available as part of package configuration:

Merge

During installation by a subscriber:

• New Package items are added to the subscribers' database.
• Package items that were modified by the subscriber are not affected.
• Items in the previous package that were deleted by the packager are not removed.
• If the subscriber has created a new platform element with the same name as an item included in the package...__TBD__

Overwrite

During installation by a subscriber:

• New Package items are added to the subscribers' database
• Package items that were modified by the subscriber are replaced
• Items in the previous package that were deleted by the packager are removed.
• If the subscriber has created a new platform element with the same name as an item included in the package, the subscriber's version is replaced by the packaged item.

Those principles apply to these package items:

• Classes
• Dashboards
• Pages
• Reports
• Static Resources
• Tab Preferences
• View Preferences
• Web Tabs
• Object aspects:

• Business Rules
• Document Templates
• Forms, Layout Rules, Form Scripts, and Custom Form Actions
• Fields and Field Scripts
• Indexes
• Macros
• Validations

__TBD: What about these? (Are these statements accurate?)

{__