Difference between revisions of "Overwrite Previous Package"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 6: | Line 6: | ||
:;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 | ::*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 overwrites the subscriber-created items)<noinclude> | ||
[[Category:Tenant Capabilities]] | [[Category:Tenant Capabilities]] | ||
</noinclude> | </noinclude> | ||
Revision as of 01:36, 4 March 2015
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, 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 overwrites the subscriber-created items)