Difference between revisions of "Overwrite Previous Package"
From LongJump Support Wiki
imported>Evelyn m |
imported>Aeric |
||
| Line 1: | Line 1: | ||
The ''Overwrite Previous Package'' option provides Publishers a choice to '''Merge''' or '''Overwrite''' packages. The Merge/Overwrite choice is applied when a Subscriber installs a package. | The ''Overwrite Previous Package'' option provides Publishers a choice to '''Merge''' or '''Overwrite''' packages. The Merge/Overwrite choice is applied when a Subscriber installs a package. | ||
{{tenantfeatures|}} | {{tenantfeatures|}} | ||
;Considerations: | ;Considerations: | ||
Revision as of 19:21, 3 November 2011
The Overwrite Previous Package option provides Publishers a choice to Merge or Overwrite packages. The Merge/Overwrite choice is applied when a Subscriber installs a package.
- The Overwrite Previous Package option is managed by a Service Provider admin
- This feature is disabled, by default
- Learn more: Tenant Configuration Options
- Considerations
- If the Package is Unlocked, this option is not available
- If the Package is Locked, the Overwrite Previous Package option becomes available, and can be enabled from Manage Tenant Capabilities
- When the Overwrite Previous Package option is enabled, these options become available as part of package configuration:
- Merge
- During installation by a subscriber, the new Package items are merged with the subscribers' existing database (previous package)
- Overwrite
- During installation by a subscriber, the new Package items overwrite the subscribers' existing database (previous package)
- If the subscriber has created new items/platform elements, they are not affected (unless there is a naming conflict, in which case, the published package will overwrite the subscriber-created items)