DREL Quick Reference

This topic provides a summary of all the Data Reference Expression Language (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.) references and properties supported by TrueContext.

Info:We’re now TrueContext.

Available on all tiers:

Essentials
Advanced
Enterprise

Contents

Reference list

You can use the Data Reference Expression Language (DREL) to create expressions that reference information about form submissions, such as metadata and question answers. Use the following references to create expressions.

Info:The topic DREL Complete Reference List describes each DREL Reference in more detail.

Reference Description Properties
%a[Unique IDClosed A Unique ID refers to the specific identifier of a question, form page, form section, or Data Destination. Unique IDs are used as reference points when pulling data for conditional logic, Analytics projects, Data Destinations, and Documents.] Question answer Replace the property with the Unique ID of the question.
%c Mobile device information
Default:
[displayText]
This property displays all other properties except prontoFormsClientSoftware.
Other:
[os], [osVersion], [model], [modelNumber], [prontoFormsClientSoftware], [prontoFormsClientSoftwareVersion].
%d Submission date
Default:
[yyyy-MM-dd]
Other:
Use supported syntax to create a custom date format.
%e[Repeatable SectionClosed A Repeatable Section is a subform that contains a set of related questions. The data captured is “repeating”, because the field user can complete the same subform more than once, which creates multiple entries. Unique ID] Answers from a Repeatable Section

Replace the property with the Unique ID of the Repeatable Section.

This returns all answers from all rows in a Repeatable Section.

Info:To return more specific results or data from nested repeatable sections, add the properties described in the topic DREL Complete Reference List
%f Form name
Default:
[name]
Other:
[id]
%g Geo location
Default:
[address]
Other:
[timestamp], [coordinates], [coordinates.latitude], [coordinates.longitude], [coordinates.altitude], [accuracy], [geoSource], [success], [errorMessage], [addressDetails][secondProperty][thirdProperty].
addressDetails second properties
[street_number], [route], [locality], [postal_code], [administrative_area_level_1], [administrative_area_level_2], [country].
addressDetails third properties (optional)
[longName] (default), [shortName].
%m DispatchClosed The term "dispatch" refers to the act of sending a form to a mobile user or customer. Typically, a dispatched form includes some information pre-filled to give the recipient context for the work to be done. Dispatch can be manual or automated (using a Dispatch Data Destination or the TrueContext REST API). metadata
Default:
[notes]
Other:
[location], [latitude], [longitude], [priority], [duedate].
%o[Destination Unique Identifier][key]

Information stored as a response output after an initial Data DestinationClosed A Data Destination specifies where to send data from a submitted form. You can use Data Destinations to automate data sharing and storage, routing data to a specific service (such as email or cloud storage) in several different formats. executes.

In the DREL expression of a subsequent destination or its linked document, replace the first property with the Destination Unique Identifier of the initial destination that stores the response output.

Replace the second property with a key returned as part of a key:value pair in the third-party system response body. You can find the key name in the third-party API documentation. The key specifies the stored value in the initial destination’s response output.
%q[Unique ID] Question text Replace the property with the Unique ID of the question.
%r Form submissionClosed A form submission is a dispatched or submitted form. properties
Default:
[referenceNumber]
Other:
[id],[ language], [name], [state], [pfStatus].
%s FormSpaceClosed FormSpaces are where forms are stored and organized in the TrueContext Web Portal. A TrueContext Team may have multiple FormSpaces, depending on their needs. Admins can set FormSpace permissions to control which users have access to the forms in that FormSpace. name
Default:
[name]
Other:
[id]
%t Submission time
Default:
[HH:mm:ss]
Other:
Use supported syntax to create a custom time format.
%u User information
Default:
[displayName]
Other:
[id], [username], [name], [email], [alias].
%v Form version
Default:
[version]
Other:
[id]

Multiple properties

You can use multiple properties with the %a reference for some question types. Add multiple properties after the [Unique ID] property.

Syntax: %a[Unique ID][SecondProperty]

Question typeClosed Question type refers to the format of a question in a form, such as a text field, dropdown, audio recording, or radio button, among others. Question types are chosen when adding questions to a form in the Form Builder. Properties
Questions with comments

[comment]

Returns the question comment instead of answer.
Geo location
Default:
[address]
Other:
[success], [geoSource], [timestamp], [coordinates], [coordinates.latitude], [coordinates.longitude], [coordinates.altitude], [accuracy], [errorMessage], [addressDetails][thirdProperty][fourthProperty].
addressDetails third properties
[street_number], [route], [locality], [postal_code], [administrative_area_level_1], [administrative_area_level_2], [country].
addressDetails fourth properties (optional)
[longName] (default), [shortName].
Date and time
Default:
[yyyy-MM-dd], [HH mm ss]
Other:
You can create your custom date and time format.
Attachment
Default:
[bytes]
Other:
[filename], [contentType].
Barcode
Default:
[barcodeValue]
Other:
[barcodeType]

Related topics