Company A-fields

Integrations > Data Export > Company A-Fields

Company A-fields contain Medallia Text Analytics topics and machine-translated comments suitable for exporting and importing.

Topic fields

Topic fields are A-fields that contain Text Analytics topic information suitable for exporting.

After selecting one or more text fields that are used in Text Analytics, Experience Cloud creates these A-fields for each selected field. Labels for the created fields begin with these strings:

  • Topics for … — Contains the topics assigned to the selected field. The topics are comma-separated in the form "Topic1, Topic2, Topic3".
  • Topics original for … — Contains the original topics assigned to the selected field, before any manual changes.
  • Topics with hierarchy for … — Contains the topics hierarchy for topics with subtopics. The topics are comma-separated in the form Topic1/Topic1.1,/Topic2/Topic2.1 .
  • Topics with sentiments for … — Contains the topics and sentiments for the selected field.
  • Topics with sentiments latest for … — Contains the manually selected topics and sentiments for the selected field
  • Topics with sentiments original for … — Contains the original topics and sentiments for the selected field, before any manual changes.

When a topic name contains a comma, the value in the field is escaped with a leading backslash, like this: " bath\, towels ". Forward slashes are similarly escaped, such as " bath\/master ".

Note: There is no way to export just parent topics.

To export topic fields:

  1. On the Company A-fields screen, select the text field(s) that are processed by Text Analytics, and save the changes to create "topic" fields for the Q-field.

    Screen capture of the Topic Fields selector with "What prompted feedback" selected.

  2. In The Data to export section (export specification) on the Integrations > Exports screen, choose the Q-field and the "topic" fields associated with the Q-field.

    Screen capture of Fields to export filtered for "prompted feedback" showing four fields

    Tip: If the Q-field you select is not processed by Text Analytics, the export will not contain any data.

Translation fields

Translation fields are A-fields that contain the results of comments that have been automatically translated. The list of available comment fields is defined on the Reporting > Text Processing > Comment Translations screen. For more information, see Translating comments.

Screen capture showing a column on the left with available translation fields and a column on the right with fields selected so they can be included in import and export specs

After selecting one or more of the available comment fields, Experience Cloud creates these A-fields for each selected field, and labels for the created field begin with these strings:

  • Translation Scheme (English) for … — The service that did the translation, either Google, Systran, or Systran_then_Google.
  • Translation Status (English) for … — Status of the translations (such as TRANS_DONE).
  • Translation to English for … — Actual translation to the target language.
    Important: When using these fields to map translations with Auto Importer, we recommend using the created fields that follow this format: a_translation_to_english_.

  • Translation to 1 for ... — (duplicate of previous field) Actual translation to the target language.

These fields are also available for inclusion in an import specification on the Integrations > Data Import > Auto Importer Processors screen, listed with other A-fields.

List of available fields for Auto Importer, including company fields

Restriction: If you try to bring in a translation for a Q-field that does not have a value populated — i.e. the value of the Q-field is NULL — the import is discarded.

These fields are also available for inclusion in an export specification on the Integrations > Data Export > Exports screen, and listed with other A-fields.

List of A-fields including company fields