---
schema_version: "1"
id: b2dec701de7c6d706dcbd510abe4aab498ea790c70865a83b2f02b24f2f76ede
title: wkcc__SurveyHistory__c
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/service-cloud/workdotcom_dev/guides/wdc-cc-sforce-api-objects-wkcc__surveyhistory__c.md
canonical_url: https://developer.salesforce.com/docs/service/workdotcom-dev/guide/wdc-cc-sforce-api-objects-wkcc__surveyhistory__c.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 52c2341c16ed77cc0908e14c9c696cb244d6749865938f66e7cebc4b5bbad2a5
products:
  - Work.com Developer Guide
  - Service Cloud Developer Content
---

# wkcc\_\_SurveyHistory\_\_c

Represents historical data from a specific sending of a survey. The data includes the name of the survey, when it started to be sent out, the schedule in force (if any), and the status of the sending operation. The history provides an audit trail that can be used for monitoring and troubleshooting survey issues. This object is available in API version 49.0 and later.

## Supported Calls

`create()`, `delete()`, `describeLayout()`, `describeSObjects()`, `getDeleted()`, `getUpdated()`, `query()`, `retrieve()`, `search()`, `undelete()`, `update()`, `upsert()`

## Fields

<sfdocstbl><table><col /><col /><col /><col /><thead><tr><th>Field</th><th>Type</th><th>Properties</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>string</td><td>Autonumber, Defaulted on create, Filter, idLookup, Sort</td><td>An autogenerated number prefixed by <code>SH-</code> that uniquely identifies the history.</td></tr><tr><td>OwnerId</td><td>reference</td><td>Create, Defaulted on create, Filter, Group, Sort, Update</td><td>The user who owns the survey schedule in force for this survey send. Not applicable for surveys sent without a schedule.</td></tr><tr><td>wkcc\_\_EndDate\_\_c</td><td>dateTime</td><td>Create, Filter, Nillable, Sort, Update</td><td>The date and time that the system finished sending out the surveys. <p>When surveys are sent to many recipients, they can be sent out in batch jobs. The date and time shown indicate when the last batch job of surveys finished running.</p></td></tr><tr><td>wkcc\_\_StartDate\_\_c</td><td>dateTime</td><td>Create, Filter, Nillable, Sort, Update</td><td>The date and time that the system started sending out the surveys. <p>When surveys are sent to many recipients, sometimes they can be sent out in batch jobs. The date and time shown indicate when the first batch job began sending out surveys.</p></td></tr><tr><td>wkcc\_\_Status\_\_c</td><td>picklist</td><td>Create, Filter, Group, Nillable, Restricted picklist, Sort, Update</td><td><p>The overall status of the sending operation.</p><p>Possible values are:</p><ul><li><p><code>Failed</code></p></li><li><p><code>Processing</code></p></li><li><p><code>Succeeded</code></p></li></ul><p>When surveys are sent to many recipients, sometimes they can be sent out in batch jobs. If any one of the batch jobs fails, the status of the overall send is <code>Failed</code>.</p></td></tr><tr><td>wkcc\_\_SurveySchedule\_\_c</td><td>reference</td><td>Create, Filter, Group, Nillable, Sort, Update</td><td>For surveys sent out on a schedule, this field is the name of the schedule. For surveys sent out without a schedule, the value of this field is null.</td></tr></tbody></table></sfdocstbl>
