Recent surveys reports

Feedback > Surveying > Recent Surveys

Recent surveys reports displays the field values for the more recent 1,000 surveys records from each of these categories:

Anonymous Surveys — Completed surveys submitted from Anonymous surveys links.
Completed Surveys — Completed surveys. For a report about surveys generated, see Survey batches.
Records — Modified survey records (all survey record types; see e_survey_type for details).

Select a survey from the list on the left. You can filter the list by survey, or by substring search. The report lists all the available E-Fields and Q-Fields, in alphabetical order. Most fields will be empty.

Junk survey records

Warning: Junked records may not be recoverable; assume data will be lost forever once junked.

Administrators should first consider other solutions, such as excluding records, for ignoring records to avoid the risk of irrecoverable data. For more information, see Exclude surveys.

Junking survey records makes records invisible to Medallia Experience Cloud and they cannot be changed to any other state.

Junking a record is not the same as excluding it: excluded records are hidden only from reports and can be easily restored, whereas junked records are very difficult to restore, are sometimes not recoverable at all, and are invisible to the entire Experience Cloud. For more information on excluding records, see Responses reports. For more information about the JUNKED status, see Survey status (e_status).

Unjunking records is expensive and time consuming, so consider the following before junking a record:

To make records invisible in Reports, exclude the records or use a flag to hide them from the user's data view.
To stop sending Reminder emails, set the survey status (e_status) to DELIVERED_NO_REMINDER.
To prevent survey takers from completing the survey, you can expire or exclude the survey.
If junking is the only option, always verify you are junking the correct record.

When a record is junked, any Alert associated to it is purged and timers associated with the alert are removed — so no overdue or escalation emails will go out. A survey taker who tries to access a junked survey gets an error message instead because the survey is no longer available.

To manually junk a survey record:

Select the Records tab at the top
Select a survey from the list on the left.
Scroll to the bottom and click Junk this survey

To junk many records in bulk, use the JunkSurvey Import processor to update existing records and change their e_status field value to 7 JUNKED. These processors take individual Survey IDs as inputs.

<import-spec columnsCheck="ALLOW_EXTRA_OR_MISSING_COLUMNS" name="Junk Survey AI">
    <input-column heading="Survey ID" />
    <output-column-group pluginName="JunkSurvey" recordUpdateMode="CREATE">
        <output-column>
            <constant value="surveyid" />
            <target-field fieldId="surveyid_field" fieldName="Survey ID Field" requiredness="REQUIRED" type="STRING" />
        </output-column>
        <output-column>
            <input-column heading="Survey ID" />
            <target-field fieldId="surveyid_value" fieldName="Survey ID Value" requiredness="REQUIRED" type="STRING" />
        </output-column>
    </output-column-group>
</import-spec>

To unjunk many records in bulk, use the UnjunkSurvey Import processor to update existing records and change their e_status field value to 1 COMPLETED.

<import-spec columnsCheck="ALLOW_EXTRA_OR_MISSING_COLUMNS" name="Unjunk Survey AI">
    <input-column heading="Survey ID" />
    <output-column-group pluginName="UnjunkSurvey" recordUpdateMode="CREATE">
        <output-column>
            <constant value="surveyid" />
            <target-field fieldId="surveyid_field" fieldName="Survey ID Field" requiredness="REQUIRED" type="STRING" />
        </output-column>
        <output-column>
            <input-column heading="Survey ID" />
            <target-field fieldId="surveyid_value" fieldName="Survey ID Value" requiredness="REQUIRED" type="STRING" />
        </output-column>
    </output-column-group>
</import-spec>