Set Up a Salesforce Repeatable Destination

A Salesforce Repeatable DestinationClosed A Repeatable Destination is a ProntoForms Data Destination that sends data from a Repeatable Section to a field-based, third-party system. sends multiple lines of data from a Repeatable SectionClosed A Repeatable Section is a type of section that contains sets of questions that the field user can answer multiple times, “repeating” the process as needed. For example, the field user can answer the same set of questions for each piece of equipment that they need to inspect. to Salesforce. You can configure a standalone Salesforce Repeatable DestinationClosed A Repeatable Destination is a ProntoForms Data Destination that sends data from a Repeatable Section to a field-based, third-party system. or link a Repeatable Destination to a “parent” Salesforce record. For example, you can link a list of required parts to a parent Salesforce Order record. This topic describes the steps required to correctly configure a Salesforce Repeatable Destination.

Available on the Advanced and Enterprise tiers:



  1. Your ProntoForms account must be on the Advanced or Enterprise tier.

  2. You must be either

  3. Ensure that you meet the prerequisites to Set up a Salesforce Data Destination.

  4. You must have already set up a Salesforce Connection.

Supported Data Destinations

You can configure any of the following Salesforce Data Destinations as repeatable:

  • Salesforce Account

  • Salesforce Case

  • Salesforce Contact

  • Salesforce Lead

  • Salesforce Standard, Custom, or Big Object

Info:The topic Set Up a Salesforce Data Destination describes all of the configuration options in detail.

Steps to set up a Salesforce Repeatable Destination

  1. In the ProntoForms Web PortalClosed The ProntoForms Web Portal is a web application used to manage security settings, forms, FormSpaces, other users, Data Sources, and Data Destinations., go to manage forms > Data Destinations.

  2. Select an existing Salesforce Data Destination or create a new one. Make sure you select a supported Data Destination.

  3. Configure the Destination Basics settings. In the Destination Type section, select the option to make the destination repeatable.

    Destination Basics tab, with option to "Use as a Repeatable Destination for a Repeatable Section" selected

    Note:To prevent errors and other unexpected results, you can’t change this to a regular destination once it’s linked to a form. This rule applies to forms in any state (Active, DraftClosed A draft form is a partially filled-out form saved on a device, or a preliminary version of a form that's been saved but not deployed in the Form Builder., or Archived). To link to a different Repeatable Section or change the destination type to Regular, first remove the destination from all linked forms.

  4. Enter the unique identifier of the Repeatable Section that you want to link to this destination.

    Tip:Ensure that you enter the correct ID. Remember, if you change a section unique ID, the linked destination does not automatically update.

  5. Do you want the submitted data to link to a parent record in Salesforce?

    • If no, go to step 6.

    • If yes, set up the parent-child relationship on the field mapping tab of your Salesforce destination. You can do this in one of two ways, as described in the following table.

    Method Works when Example
    %a DRELClosed Data Reference Expression Language (DREL) is used to get form data and metadata and add it to a string, such as dates, usernames, or answers to questions in forms. reference

    Records and relationships already exist in your Salesforce org. Use a Data Source to pass the record IDs to questions in your form. Then, you can use the %a DREL reference to extract that data and map it to your Salesforce fields.

    Example of a Salesforce Standard, Custom, or Big Object Data Destination with the "ID" question  mapped to the existing Salesforce Case ID
    %o DREL reference

    You run two or more destinations sequentially to create or update a parent record. When a destination creates or updates Salesforce records, Salesforce responds with the record IDs.

    In the parent destination, select the option to Store all response outputs… to store these Salesforce IDs.

    Note:The parent destination must be a Regular destination.

    In the child Repeatable Destination, use the %o DREL reference to map the output from the parent destination to your Salesforce field:



    %o is the DREL expression to reference the stored output of the parent destination
    DestinationID is the unique ID of the parent destination in ProntoForms
    key is the key returned as part of a key:value pair in the Salesforce API response body, typically id.

    Note:Remember, if you change the parent destination unique ID, the child destination does not automatically update.

    Example of a Salesforce Standard, Custom, or Big Object Data Destination with the Order "Id" field mapped to the response from the parent "Order" destination
  6. Complete the configuration, and then Save the destination.

  7. In the ProntoForms Form Builder, add the relevant destinations to a form in the order you want them to execute. Parent destinations should be before (above) the child destinations.

    Parent destination "Order" above Child destination "Parts List"

    Note:You can’t attach documents to a Repeatable Destination. This prevents duplication of the same document across multiple records.

How to avoid configuration errors

Repeatable Section IDs

If you change a unique ID of a Repeatable Section, you must also change it in any Repeatable Destinations that reference it.

Parent destination IDs

If you change the unique ID of a parent destination, you must also change it in any child destinations that reference that parent.

Changing between Regular and Repeatable Destinations

You can’t change the type of destination if that destination is “in use”. This applies when a destination is linked to a form that’s Active, Draft, or Archived.