Navigating to the new page

The Experience Cloud Mapping page relies on the latest version of the Command Center UI. The migration of properties to the UI is ongoing, and currently some parts of the UI are not migrated. As such, the navigation menu only shows the link to the Experience Cloud mapping page when you are on a Command Center page that has been migrated to the new UI. For example Forms is currently on the legacy UI so the EC Mapping link does not appear from that page. Pages currently using the new UI include, Rule Engine, Custom Parameters, User Behavior Triggers, Advanced Settings (if enabled), and Approved Domains (if enabled).

When you open the EC Mapping page it displays a list of the current mapping between Experience Cloud and Digital.

Filter the list of mappings to see them across your properties and forms. Select one option in each category: EC Type, Usage, Share Level, Property. If you select "Account" share level then the Property filter is not visible.

For example to find a list of all text fields available for use in survey forms, choose to filter by "Text" (EC Type), "Form Field" (Usage), and "Share Level" (Account). You cannot select multiple options within a single category. For example, you cannot select "Email" and "Text" under EC Type to find a list of all email and text fields

See fields by the selected type. This list also defines the types of fields that are currently supported in the integration to Experience Cloud. If a field type is not listed, it means that it cannot currently be used in Digital Feedback.

See fields available for use in surveys with Form Fields, fields available for custom parameters Custom Parameter, or both.

See fields available for the entire account, fields available to specific properties, or both.

List all properties in the Digital account..

Select an individual property or any of the available properties..

The columns show the different mapping's values.

• EC Key: The field name in Experience Cloud
• EC Type: The field’s ContentKind in Experience Cloud
• EC Friendly Name: This name appears on your field mapping drop-down
• Usage: The usage of the field in Experience Cloud
• Share Level
• Property Names: The properties that use this field
  • If share level is Account, no property names are displayed

Actions

Hover the cursor over a row and these icons are visible.

• Pencil: Open the Edit Mapping to MEC options. Use this menu to update the EC Friendly Name or the Share Level. You cannot edit the EC Key or the EC Type.
• Trash Can: Initiate deletion of the field from the Reusable Field Library

Adding fields

To make minor additions to the reusable field mappings, use the Command Center interface. Alternatively, to make larger changes to the reusable field mapping use the bulk operations.

1. Add fields individually by clicking New Mapping.

   

2. "New Mapping to MEC" opens in a side panel. Provide this information:

   • EC Key
     • Full field keyname - with e_ or q_ prefix
   • EC Type
     • Must match the ContentKind of the field in Experience Cloud and is validated upon upload
     • Incorrect Content
   • EC Friendly Name
   • Usage
   • Share Level

   

3. After providing all required details, click the Create button.

   You cannot click Create if any of the required details are missing.

   

   

4. If the selected EC Type is correct, a success message appears and the field appears in the Experience Cloud Mapping table.

   The field is now available for use in survey or custom parameter configuration.

   

5. If the selected EC Type is incorrect, an error message appears after clicking Create. You need to identify the correct EC Type by referencing Experience Cloud, and then repeat the process of adding the mapping.

   

Bulk edits

To make a lot of changes to the reusable field mapping, it can be more convenient to work with the data in an external tool such a spreadsheet. Use the import and export to save the reusable field mapping as an XLSX format file. Then make the changes to the fields using your spreadsheet editor and import the modified reusable field mapping.

Export reusable field mapping

Use the Export function to fetch an XLSX file with the reusable field mapping, showing the required column headers.

1. Export a table of all reusable field mappings in the library by clicking the Export button.

   

   The mappings are exported to an XLSX file that is downloaded to your local machine.

2. To make bulk changes to the reusable field mapping load the XLSX file in a spreadsheet editor.

   

3. The exported file has these columns:

   • EC Key
   • EC Type
   • EC Friendly Name
   • Usage
   • Share Level
   • Properties (populated only if Share Level is set to "Properties")

Import (Bulk Mapping)

Use the Import function to add fields to the reusable field library by uploading an .xlsx file. You should export the existing library to fetch the correct format (.xlsx) and column headers.

The required column headers are (in order, from left to right):

1. EC Key
2. EC Type
3. EC Friendly Name
4. Usage
5. Share Level
6. Properties (only required if Share Level is ‘Properties’)

The uploaded file must also have the sheet title labeled as ‘Reusable fields’. This is already set by default in the export file.

Import: Allowed Values

Import: Adding new fields

1. Export the current list of fields to fetch the correct file format and required column headers.

   

2. For each new field you would like to add, provide the requested details in a new row.

   

3. Add new fields by adding to the end of the existing list.

   

4. You can also add new fields by removing the existing fields in the list (rows with the gray shaded cell) and keeping the column headers. If you have no updates to make to the existing list of fields, Medallia recommends removing them from the Import file and only including the new fields you would like to add.

   

5. When populating the file with new fields, you must fill out all required details:

   • EC Key
   • EC Type (Reference this table for the values to use - they are slightly different from the values in the Command Center picklist)
   • EC Friendly Name
   • Usage
   • Share Level
   • Properties (populated only if Share Level is set to "Properties")

   

6. Delete all empty rows.

   Uploading empty rows can result in extra error messaging, indicating that the empty row was not processed. This has no impact on rows successfully processed, but can be confusing to see.

   

7. Save the Import file after adding all desired fields and verifying that all entered values are correct. Note the case sensitivity of some values.

8. To import the file, click Import button on the Experience Cloud Mapping screen, and select your updated import file

   

9. A success message is displayed if all required values pass validation with Experience Cloud. New fields added become visible in the Experience Cloud Mapping table, and are now available for use in configuration

   

Import: Error Messages and Troubleshooting

During the import process you could encounter these errors.

• If you have been logged out due to timeout in the Experience Cloud instance and attempted to add a field, this error message is displayed.

  

  To proceed, you need to re-authenticate to the Experience Cloud instance.

• If there are rows that fail the Import validation, you are provided with an error message and link to download an error log file

  

  The error log file can be downloaded as a plain text (.txt) file.

  The file identifies the sheet and row where the error took place for you to troubleshoot further.

  

Import FAQ

• Can I use the Import function to create new fields?
  • No. The Import functionality is to make existing Experience Cloud fields available for usage in Digital Feedback survey form and custom parameter configuration.
    • Create new fields in Experience Cloud
• Can I use the Import function to remove fields from the library?
  • No. The Import function can only be used to edit attributes of existing fields (See which attributes are editable after creation) or to add new fields to the library.

Removing a field from the library

When a field is removed from the library, it is no longer available for selection in the Form Builder or Custom Parameter configuration.

Existing usages of the removed field in Form Builder or Custom Parameter configuration are not affected, and the linked components remain mapped to the selected field.

1. Remove fields from the library by clicking on the trash can icon in the Action columns.

   

2. You are prompted to confirm that they want to delete the field mapping.

   

3. After clicking Delete, the field is removed and a success message is displayed

   

Reference

Medallia recommends mapping questions to the field types listed below:

Field Types by Parameter Type

Medallia recommends mapping custom parameters to the fields listed below: