Built-in Data

Built-in Data

Every form entry includes a number of built-in data fields that are available for use in your templates and connectors.

Additionally we provide built-in fields to access to some company level settings like the name of your organisation. Built in values can be used in your templates by using the {{%BuiltInName}} syntax.
For example if you want to display the entry id as per the table below you would use {{%ENTRYID}} in your template or connector.

The built-ins available are as follows:

Company Information

PRIVATETOKEN
Inserts the private token value found in your Organization Setup page. 

ORGID
Inserts the unique integer identifier of your company account on our platform.

ORGLETTERHEAD
Inserts your organisation letterhead image as setup in the Organisation Setup.
If no letterhead is found, the organisation logo image is used (if any exists).

ORGNAME
Inserts the name of your company as setup in the Organisation Setup.

ORGCREATEDATE
Returns the Unix Time (Epoch Time) to calculate the time from when your organization’s account was created.

User Information

USEREMAIL
Inserts the email address of the user that completed the form.

USEREXTERNALID
Inserts the external Id of the user that completed the form.

USERFIRSTNAME
Inserts the first name of the user that completed the form.

USERLASTNAME
Inserts the last name of the user that completed the form.

LASTLOGINDATETIME
Returns the Unix Time (Epoch Time) to calculate the time since the last time the currently logged-in user logged in.

USERCREATEDATE
Returns the Unix Time (Epoch Time) to calculate the time since the currently logged-in user account was created.

USERROLE
Returns the user type of the currently logged-in user, e.g. Standard, Premium, Edge.

Entry Information

COMPLETELAT
Inserts the GPS latitude (in decimal degrees) of the user when completing the entry.

COMPLETELON
Inserts the GPS longitude (in decimal degrees) of the user when completing the entry.

COMPLETEMAP
Inserts a map image for the GPS co-ordinates of the user when completing the entry.

COMPLETETIME
Inserts the date and time that the user completed the Form entry (i.e. clicked upload in the app, regardless of connectivity).
The correctness of this value is dependent on the users device time settings.

COMPLETETIMEUTC
The same as COMPLETETIME, but inserts the date and time in UTC.

ENTRYGUID
Inserts the unique identifier string of this entry, without hyphens (i.e. 00000000000000000000000000000000).
The identifier string is unique across all forms and all entries.

ENTRYGUIDFULL
Inserts the unique identifier string of this entry, including hyphens (i.e. 00000000-0000-0000-0000-000000000000).
The identifier string is unique across all forms and all entries.”

ENTRYID
Inserts an incremental calculated integer number for this form entry.
The entry id for a specific entry is calculated as the current highest entry id for the form screen (all versions) plus one.

RECEIVEDTIME
Inserts the date and time that the form entry was received by our server. This may differ significantly from the “CompleteTime” value depending on the connectivity of the app.

RECEIVEDTIMEUTC
The same as RECEIVEDTIME, but inserts the date and time in UTC.

STARTTIME
Inserts the date and time that the user started the form entry. The correctness of this value is dependent on the users device time settings.

STARTTIMEUTC
The same as STARTTIME, but inserts the date and time in UTC.

    • Related Articles

    • Built-In Templates

      Our platform offers a few built-in templates that can be used when exporting form-captured data in PDF. Even though you can fully customize your outputs using Word or Excel files, the following new and improved built-in templates may come in handy ...
    • Replicating Built-in App Screens

      The apps you build will have a set of standard/default Screens included by default. These being: Settings screen (for changing password, forcing sync, logging out) Saved Entries screen (list of in-progress/saved Form entries) Tasks screens (list of ...
    • Nesting Repeatable Data

      Capturing structured, repeatable data is essential for many workflows, from property audits to equipment inspections. However, some scenarios require additional repetition, such as rooms within apartments or components within a machine. The most ...
    • Form Captured Data FAQ

      I have published a new Form version, but I am still seeing some Data entries coming in against the old Form version. Shouldn’t the users app have updated to the latest version automatically? The system will automatically update mobile users with the ...
    • FAQ- Data Captured

      Q: I have published a new Form version but I am still seeing some Data entries coming in against the old Form version. Shouldn't the users app have updated to the latest version automatically? A: The system will automatically update mobile users with ...