Skip to content

Processing responses onto records

A response does not go straight onto your Salesforce records. It waits in the responses console first. Processing is the step that writes it onto Contacts, Cases, Leads, or whatever the form targets.

For each response, processing:

  • writes the answers onto records, using each field’s mapping,
  • updates an existing record instead of creating a new one, when a match key is set up and the answers match,
  • applies the form’s record type to new records,
  • links any uploaded files, however long the response waited before processing,
  • creates a child record for each row of a repeating group.

You can check all of this before you run it. Click the row in the console to see What processing would do. See The responses console.

Editing a response's answers before processing, with Save correction and Back to preview

While a response is Received or Failed:

  1. Click the row, then Edit answers in the panel header.
  2. Change what needs changing. Questions the respondent left out are listed too, required ones first, so you can fill in a missing answer.
  3. Click Save correction. (Back to preview leaves without saving.)

Your corrections sit on top of the original. The answers the respondent sent are kept unchanged for the record, and processing uses your corrected values. Each correction you save builds on the last one. Saving a correction on a Failed response puts it back to Received, ready to retry.

Blank answers are skipped when processing. Clearing an answer here will not blank that field on a matched record.

Two responses selected with the Process Selected button and the summary from the last run

  • Each row has one button: Process while it is Received, Retry once it has Failed.
  • To run several at once, tick the rows and click Process Selected. A summary then says n of m processed successfully.
  • Processing runs with your permissions. If you cannot create or edit the target records, processing fails with that error.
  • The summary names anything it could not record. This only happens if someone can create the target records but cannot update the response itself, which is possible only with a permission set or profile you built yourself (Edit on responses without Modify All). The summary names the records created, so nothing is processed twice. Sliick Forms Admin and Sliick Forms Operator are not affected.
  • If your own validation rule or automation blocks the response from being marked processed, the whole run is undone. No records are left behind without their response. The error is logged.
  • Suspected duplicates and responses that failed validation are skipped until someone marks them genuine or accepts them. See The responses console.
  • Responses in a run are processed oldest first. If two of them match the same record, both update it and the later one wins where they disagree. See Matching.
  • A file that cannot be attached leaves a note on the response, in its Result / Error column. The response is still marked processed, and the record is still created.
  • You can also process responses from a Flow. See Process responses from a Flow.

Sliick Forms adds one Flow action, Process Sliick Form Submissions, under Sliick Forms in Flow Builder. It does what Process does in the console, for the responses you give it.

  • Input: submissionIds. The Record ID of a Form Submission, the record each response is stored as. In a record-triggered Flow on Form Submission, pick Triggering Form Submission > Record ID.

  • Output: output. One line of text per response, starting with:

    • Completed: when the records were created or updated,
    • Failed: with the reason, when processing failed. The response is marked Failed in the console, ready to Retry,
    • Skipped: for a suspected duplicate or a response that failed validation. Processing it again changes nothing until someone marks it genuine or accepts it.

    A response the running user cannot see returns Failed: submission not visible to the running user.

  • It runs with the permissions of the user the Flow runs as, just as Process runs with yours.

  • Permissions to start the Flow. A screen flow, or a flow called over REST, needs Salesforce’s Run Flows permission, which no Sliick permission set grants. System Administrators normally have it. Record-triggered and scheduled flows don’t need it.

To create or update a form’s records as soon as each response arrives, see How to Create or Update Salesforce Records Automatically from Form Responses.

  • A date and time answer with no time zone is read in your org’s default time zone. Before version 0.9.0 it was read as UTC, so a response received before that upgrade may match a different record.
  • A Date answer mapped to a Date/Time field is written as midnight in the respondent’s time zone. That field cannot be used as a match key.
  • A date Salesforce cannot store still fails processing. Correct it with Edit answers, then retry.

The reason is shown on the row. Check these in order:

  1. Your own access to the target object and every mapped field. You need it on the Salesforce objects the form writes to, not only on Sliick Forms.
  2. A mapped field that no longer exists. If a target field was renamed or deleted in Setup, the mapping breaks without warning until processing runs.
  3. A required field the form never collects. The record cannot be created. Add a hidden field with a default value to fill it. See Mapping a starter form.
  4. A validation rule on the target object that rejects the values.
  5. Person accounts. Orgs that use them can meet two specific errors. See Person accounts.

Fix the cause, then click Retry. Nothing is lost. The original answers are kept exactly as sent, and you can fix them with Edit answers first if the answers were the problem.

Failed responses are counted on the dashboard’s Failed processing tile, which opens the console filtered to failures. They are also listed in Needs attention.

Answers a respondent never saw are not written

Section titled “Answers a respondent never saw are not written”

Processing only writes answers to questions the respondent could see. If a question was hidden by a visibility rule, its answer is not written to your records. The same goes for a file uploaded to a hidden question, and for a repeating-group row whose own rule was false. The response itself still keeps everything that arrived, so you have a full record.

The exception is a Hidden Field with a default value. That is a fixed value you set, not an answer, so it is written on every response.