---
schema_version: "1"
id: 311b0fa6d9096d79fe9ddcd2b797702b6a47b5968245136c1424c40b298dd743
title: Content Slot Object Import/Export in B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_content_slot_object_import_export.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_content_slot_object_import_export.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 789118ab8e8d94eb312c232f747f0b0cfd5a7ac17f6f31ee824fc6590c8dbd07
description: Using Business Manager, import existing content slot configurations to use with a new instance, and export them for transfer between instances. The slots themselves aren’t imported or exported, but page templates define them (in UX Studio). Slot configurations only reference those slots (using the slot ID). Within Business Manager, the elements in the slot.xsd control the visibility of a slot.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Content Slot Object Import/Export in B2C Commerce

Using Business Manager, import existing content slot configurations to use with a new instance, and export them for transfer between instances. The slots themselves aren’t imported or exported, but page templates define them (in UX Studio). Slot configurations only reference those slots (using the slot ID). Within Business Manager, the elements in the slot.xsd control the visibility of a slot.

A slot configuration can belong to zero or one site. A slot configuration that doesn't belong to a site is like a reusable part for the site to use. You can assign a slot configuration to no campaigns or promotions or to one campaign or promotion. The schedule, rank, and qualifier elements are part of the assignments.

 
| Elements or attributes | Impact |
| --- | --- |
| <slot-configuration> | When importing a <slot-configuration> element in MERGE mode, the system checks to see if there’s an existing slot configuration with the same ID in the current site domain. If so, the import process updates the existing one; if not, the import process creates one. |
| <rank>, <schedule> or <customer-groups> | If the import file includes any of the deprecated elements <rank>, <schedule>, or <customer-groups>, the system can only update them if there’s an explicit SlotConfigurationAssignment between the slot configuration and the site. If one exists, the import process updates those attributes of the assignment;. If none exists, the import logic logs a warning. |
| <slot-configuration-assignment> | When importing a <slot-configuration-assignment> element in MERGE mode, the system checks to see if there’s an existing assignment. The system checks between the specified slot configuration (identified by a compound key consisting of slot-id, context, context-id, and configuration-id) and the current site (derived from the import/export context, not specified in the file). If an assignment exists, it's updated; otherwise, the system creates one. |
| <slot-configuration-campaign-assignment> | When importing a <slot-configuration-campaign-assignment> element in MERGE mode, the system checks to see if there’s an existing assignment between the specified slot configuration and the campaign (specified by campaign-id). If an assignment exists, it's updated; otherwise one is created. If you perform the import in a different import mode, the usual modified semantics apply. |
| <mode> | There’s a new _mode_ attribute in the existing <slot-configuration> element. This mode attribute is used for deleting individual objects without doing a full DELETE mode import. The <slot-configuration> element offers special _wildcard_ behavior for deletion. You can omit the _context,_ _context-id_, and _configuration-id_ in delete mode. Use this technique to delete multiple slot configurations simultaneously. |
| <slot-configuration-assignment> and <slot-configuration-campaign-assignment> | The new elements <slot-configuration-assignment> and <slot-configuration-campaign-assignment> support a delete mode, but not a _wildcard_ deletion, such as described previously. With this method, Only delete one assignment at a time. As a result, the attributes _context,_ _context-id,_ and _configuration-id_ are required for these elements. |

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note Parent slots for deleted configurations aren’t deleted as part of this process, even if the import results in 0 slot configurations.

## Business Manager Import Location

**Online Marketing** | **Import & Export**

## Pipelets

- ImportSlots
- ExportSlots

## Import Content Slot Configurations

Import B2C Commerce slot configurations.

1. Click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **site** | **Merchant Tools** | **Online Marketing** | **Import & Export**.
2. In the Content Slot section, click **Import**.
3. Select an import file from the list and click **Next>>**.
4. B2C Commerce validates the schema file.
    - If the schema file validation is unsuccessful, examine the file for errors and start over.
    - If the validation is successful, click **Next>>**.
5. Select an import mode:
    
    <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small "><tbody><tr class=""><td style="vertical-align:top;" headers="d240624e268-option" id="d240624e272">Merge</td><td style="vertical-align:top;" headers="d240624e268-desc d240624e272">Updates existing database objects and creates objects based on XML import file.</td></tr><tr class=""><td style="vertical-align:top;" headers="d240624e268-option" id="d240624e281">Update</td><td style="vertical-align:top;" headers="d240624e268-desc d240624e281">Updates existing database objects only (doesn't create ones).</td></tr><tr class=""><td style="vertical-align:top;" headers="d240624e268-option" id="d240624e290">Replace</td><td style="vertical-align:top;" headers="d240624e268-desc d240624e290">Deletes and then recreates existing database objects; creates objects based on XML import file.</td></tr><tr class=""><td style="vertical-align:top;" headers="d240624e268-option" id="d240624e299">Delete</td><td style="vertical-align:top;" headers="d240624e268-desc d240624e299">Deletes slot configurations referenced in the file; parent slots aren’t deleted.</td></tr></tbody></table>
6. Click **Import**.
    
    The Import & Export page reappears, where you can monitor the status of the import job.

### Content Slot Import Modes in B2C Commerce

Learn how the DELETE, UPDATE, MERGE, and REPLACE import modes change content slot configurations when you import a content slot file, and how to diagnose unexpected import results.

- Export: enter a valid file name (no special characters). If the file name doesn't end in ".xml", the system appends the extension.
- 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:

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
            <colgroup>
              <col style="width:20%">
              <col style="width:40%">
              <col style="width:40%">
            </colgroup>
            <thead class="slds-text-title_caps ">
              <tr class="">
                <th scope="col" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" id="d240624e374">Mode</th>
                <th scope="col" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" id="d240624e377">Element/situation</th>
                <th scope="col" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" id="d240624e380">Behavior</th>
              </tr>
            </thead>
            <tbody>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">DELETE</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">Slot configurations</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">If referenced in the file, the system deletes it from the
                  database.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If you specify only a slot-id</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">All slot configurations for the slot with that id are
                  deleted.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If you specify a slot-id and context</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">All slot configurations for the slot in that context are
                  deleted.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If you specify slot-id, context, and context-id</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The system deletes all slot configurations for the slot in
                  that context, with that context-id.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If a slot-id, context, context-id, and configuration-id are
                  all specified</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The system deletes the one slot configuration for the slot in
                  that context, with that name, if it exists.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If a context, context-id, or configuration-id specified, but
                  not the slot-id</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The system ignores the missing element with a warning.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">UPDATE</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">Standard UPDATE mode</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The system updates existing slot configurations referenced in
                  the file.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If the slot-id, context, context-id, and configuration-id
                  match a slot configuration</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">Only the specified elements result in updated properties of
                  that configuration.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If the slot-id, context, context-id and configuration-id don't
                  match a slot configuration</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The system ignores the element with a warning.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If you specify multiple slot configurations as the
                  default.</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The last slot configuration is set to the default and a
                  warning appears in the log.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">MERGE</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">Standard MERGE mode</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">
                  <p>The system updates existing slot configurations referenced in the file and
                    inserts any new slot configurations in the file.</p>
                  <p>The defaults for optional MERGE properties are:</p>
                  <ul class="listbullet">
                    <li class="listbullet">enabled-flag - false</li>

                    <li class="listbullet">default - false</li>

                    <li class="listbullet">schedule - continuously</li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">For the update case</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">
                  <p>The same behavior as for the UPDATE mode.</p>
                  <p style="margin-bottom:0;">Required properties are: slot-id, context, context-id, configuration-id and
                    the template.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">For the insert case</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">Provide all required properties, or the system ignores the
                  slot configuration with a warning.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If you specify multiple default configurations</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The last slot configuration is set to the default and a
                  warning appears in the log.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">REPLACE</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">Standard REPLACE mode</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">
                  <p>The same as for MERGE mode, except that the update of existing slot
                    configurations is as if they were first imported in DELETE mode.</p>
                  <p style="margin-bottom:0;">This means that the system deletes the existing slot configuration and
                    inserts a new one with the provided data. The system reuses the location
                    where the slot configuration was stored.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If optional element properties elements are not
                  specified.</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The defaults take effect, even if the default values are
                  different than the values in the slot configuration being replaced.</td>

              </tr>
              <tr class="">
                <td data-label="Mode" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e374 ">&nbsp;</td>

                <td data-label="Element/situation" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e377 ">If you specify multiple default configurations</td>

                <td data-label="Behavior" class="slds-cell-wrap" style="text-align:left;vertical-align:top;" headers="d240624e380 ">The last slot configuration is set to the default and a
                  warning appears in the log.</td>

              </tr>
            </tbody>
          </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

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

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

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, the system creates a slot that contains the referenced slot-id, context and context-id, if appropriate. No problem results because no template actually references the slot.

#### Troubleshooting Slot Import

If an import produces unexpected results, check the file against these conditions:

- Did you run an import on slot configurations with references to slots that aren't in the template? You can get a data warning, but the slot configurations are still imported as place holders.
- Did you have slot configurations with references to slots in the template, but the slots are later removed from the templates? Those slot configurations don't appear in Business Manager.

## Export Content Slot Configurations

Export B2C Commerce content slot configurations.

1. Click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **site** | **Merchant Tools** | **Online Marketing** | **Import & Export**.
2. In the Content slot section, click **Export**.
3. Enter a name for the export file. If you don't enter the .xml suffix, it’s appended automatically.
4. Click **Finish** to submit the job.
    
    The Online Marketing > Import & Export page reappears. The job's status appears in the Status section of the page.
5. To view the job's log file, click the **Process** link in the `Status` section.
6. On the page that opens, click the **Download Export File** link in the `Export File` section to download the export file to your local machine.