Difference between revisions of "Overwrite Previous Package"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 3: | Line 3: | ||
;Considerations: | ;Considerations: | ||
*When the Overwrite Previous Package option is enabled, these options become available as part of package configuration: | *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) | :;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) | :;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) | ::*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) | ||
Revision as of 22:55, 26 February 2014
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. Template:Tenantfeatures
- Considerations
- 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)