Fields can be used in many places in the platform to collect the data you need to action, analyze, and report on. Fields can be associated with a group or person contact, or be custom to a form.
The advantage of using a specific field type versus a default text field is that you can more accurately sort and calculate data. For example, the datetime field ensures that all dates are entered in a standard format, so there is no confusion about day/month order. Number fields can be used to calculate totals, etc.
Top 4 Tips for Fields
Keep field names brief. Enter instructions and details in the Field Description.
Choose the most accurate field for your data. E.g. if the question is "How many people are in your group?" the answer should be numeric. Text allows users to enter random data like "three," "N/A," and so on, that cannot be easily sorted or used for reporting.
Avoid duplicating fields, as this will cause confusion. If you need to have variants of the same fields, be specific when naming them, such as "Home Phone" and "Mobile Phone".
Fields transfer from event to event when events are cloned into a new year. If you change data in a field on one event, it will be changed across all events. We recommend naming year-specific fields (i.e. "2022 Artist Fee") to help manage these, so in 2023 you can create a 2023 Artist Fee version that doesn't overwrite the 2022 data.
Creating fields
When creating fields, you can set a field name, type, description, group, and field- specific settings.
Below is a sample dropdown field to collect dietary requirements.
Below is a guide to field formats in Lennd.
Field Example | Field Type | Acceptable Format |
Name | Text | Any text. |
Tell us why you want to be a vendor (max 500 words). | Textarea | Any text. |
Business Email | Any text. | |
Check to confirm you have read the terms and conditions. | Checkbox | "Yes" will check the box. Leave the cell blank if you do not want to check the box. |
How many people are in your group? | Number | Any integer. Decimals accepted. |
Amount Due | Currency | Any integer. Will assume the default currency of your event. Up to 2 decimal places. Currently only supports USD. |
Please provide the date and time of your arrival. | Datetime | We will attempt to validate & parse any date-like format you attempt to import.
Without Timezone Specified yyyy-mm-ddThh:mm:ss.ffffff || 2008-09-15T15:53:00
With Timezone Specified yyyy-mm-ddThh:mm:ss.nnnnnn+|-hh:mm || 2008-09-15T15:53:00+05:00 |
Select one of the below options:
| Dropdown | Depending on the context, import may allow new options to be created. Imported values must match existing dropdown options. If dropdown field allows multiple select, options may be separated by comma e.g. "Option A", "Option B". Not case sensitive.
Note: If you have dropdown fields, you’ll need to enter an option that you have already created within the Lennd dropdown field. You cannot add new options by importing them. |
Revenue Split (%) | Percent | Any Integer. We will not do any decimal to percent calculation. We assume the number you are importing is the percentage. For example - if you upload 0.5 - we assume this means 0.5% as opposed to 50%. |
Arrival Date | Date | yyyy-mm-dd OR mm-dd-yyyy |
Phone Number | Phone | Any Length - With or without dashes |
Country | Countries | Any Text ISO Alpha-2, Alpha-3 Country Codes recommended but not required. |
Arrival Time | Time | Displays the hour as a number with a leading zero when appropriate. If the format contains AM or PM, the hour is based on the 12-hour clock. Otherwise, the hour is based on the 24-hour clock. h:mm:ss h:mm hh:mm |