---
title: "Querying on Form Responses"
slug: "querying-on-form-responses"
description: "Instructions for querying on form responses, including the form field value export."
updated: 2025-06-13T22:30:05Z
published: 2025-06-13T22:30:05Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Querying on Form Responses

When creating a form response-scoped query, or joining to Form Response in any query, you’ll be prompted to choose between querying responses for **all forms and events** or a **specific form, event, or template**. Depending upon the option you choose, different querying options are available.

## Querying form, event, or template data

The **form response** query base contains only information relating to responses to forms—for example: registration status, form submission date, or count of guests. Information about the form, event, or template itself is not immediately available from the Form Response base, regardless of whether you chose to query responses for all forms and events or a specific form, event, or template.

To access data on the form, event, or template itself within your query, add a new Join from **form response** to **form.** After creating that join, you will be able to query on data points such as the form’s title, an event’s start date/time, or its internal URL.

## Querying response data from a specific form, event, or template

When a specific form, event, or template is chosen as the base type for a form response query or join, Slate will automatically generate exports and filters based on the form fields on that form, event, or template (whether they are mapped or unmapped). You can use these exports and filters as you would any other exports and filters in Slate.

> [!NOTE]
> 📝 Note
> 
> The option to query response data from a specific form, event, or template may be limited or unavailable depending on the query base you’re joining from. For example, only Application-scoped forms will be available when joining from the Application base.

## Querying response data from all forms and events

When creating queries or reports, you may wish to query on data from multiple unique forms or templates. The **form field value** export available from the **all forms and events**form response query base simplifies accessing this data. This can be especially useful in reporting across multiple forms that collect different, but overlapping, data points.

![A screenshot of the Insert Query Part pop-up with Form Field Value selected.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image(681).png)

After selecting the form field value export, Slate will display a warning that the export requires configuration:

![Screenshot of the query builder with the Form Field Value export warning 'This export requires configuration'.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image(682).png)

Edit the export by double-clicking it or selecting the edit button. Under “Configuration,” enter the Export Key of your Form Field exactly as it displays in your form.

![Screenshots showing the export key in the form and matching configuration in the query editor.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image(686).png)

After configuring the form field value export, it will return the value associated with that export key in any form responses where a value exists.

A method used to connect multiple data tables to one another when creating a query.

An Export Key will be pre-populated for mapped form fields. If a form field is unmapped, an export key can be entered to enable querying on this field data.

Form fields are data points collected on a form; these can be text boxes, prompt-driven lists, addresses, or many other types of data. Unmapped form fields can capture data that is not essential within the larger context of the person record as they will not store back to the record. Form fields mapped to system fields will be stored back on the associated record.