Content Slot Import Modes

You can import and export content slot configurations.

Export: enter a valid file name (no special characters). If the file name doesn't end in ".xml", the extension is appended.
Import: select an import file from the list. The system performs a validation. After validation, the user can select an import mode: DELETE, UPDATE, MERGE and REPLACE.
The following table describes the import behavior:

Mode	Element/situation	Behavior
DELETE	Slot configurations	If referenced in the file, it is deleted from the database.
	If only a slot-id is specified	All slot configurations for the slot with that id are deleted.
	If a slot-id and context are specified	All slot configurations for the slot in that context are deleted.
	If slot-id, context, and context-id are specified	All slot configurations for the slot in that context, with that context-id, are deleted.
	If a slot-id, context, context-id, and configuration-id are all specified	The one slot configuration for the slot in that context, with that name, is deleted if it exists.
	If a context, context-id, or configuration-id specified, but not the slot-id	The missing element is ignored with a warning.
UPDATE	Standard UPDATE mode	Existing slot configurations referenced in the file is updated.
	If the slot-id, context, context-id, and configuration-id match a slot configuration	Only the elements that are specified will result in updated properties of that configuration.
	If the slot-id, context, context-id and configuration-id don't match a slot configuration	The element is ignored with a warning.
	If multiple slot configurations are specified as the default.	The last slot configuration is set to the default and a warning appears in the log.
MERGE	Standard MERGE mode	Existing slot configurations referenced in the file are updated, but also any new slot configurations in the file are inserted. The defaults for optional MERGE properties are: enabled-flag - false default - false schedule - continuously
	For the update case	The same behavior as for the UPDATE mode. Required properties are: slot-id, context, context-id, configuration-id and the template.
	For the insert case	All required properties must be provided or the slot configuration is ignored with a warning.
	If multiple default configurations are specified	The last slot configuration is set to the default and a warning appears in the log.
REPLACE	Standard REPLACE mode	The same as for MERGE mode, except that the update of existing slot configurations is as if they were first imported in DELETE mode. This means that the existing slot configuration is deleted and a new one inserted with the provided data. The location where the slot configuration was stored is reused.
	If optional element properties elements are not specified.	The defaults take effect, even if the default values are different than the values in the slot configuration being replaced.
	If multiple default configurations are specified	The last slot configuration is set to the default and a warning appears in the log.

Note: Exactly one configuration can be set as the default for each combination of slot-id, context and context-id.

Note: It's possible in MERGE mode to import slot configurations that reference a slot that doesn't exist. This can occur when an import occurs before the storefront templates have been changed to contain the correct <isslot> tags. In this case, a slot is created that contains the referenced slot-id, context and context-id, if appropriate. No problem results because no template actually references the slot.