Fields property

The fields of the app as an array.

Accessing all fields of the app through this property has many uses:

• Deciding which background color to use based on whether the fields of the app are valid.
• Enabling a button only if all fields of the app have been filled out.
• Collecting the labels and values of all fields of the app as a text string, for use as the body of an email.

The following sections detail how these scenarios can be realized. Skip to the examples at the bottom for the concise version.

Making the background color red if a field is invalid

The BackgroundColor property determines the background color of a screen and all screens that follow that have no explicit background color set. That means that if the background color is set for the first screen of an app, and no other screens have a background color set, the first screen determines the background color of the entire app.

We can make use of this knowledge to make the background of the entire app red, but only if at least one field of the app is invalid. This formula is associated with the BackgroundColor property of the first screen:

The formula fragment App.Fields.ValidApp,Fields,Valid returns a logical array, where TRUE indicates that the corresponding field is valid and FALSE indicates that the corresponding field is invalid. Applying the NOT function to this array negates every element, meaning that TRUE indicates that an field is invalid and FALSE indicates that an field is valid. (The ! operator would have had the same effect.)

Then, the OR function is applied to this array. It returns FALSE only if all elements of the array are FALSE. In other words, it returns TRUE if one or several elements are TRUE, meaning that it returns TRUE if one or several fields are invalid.

Finally, the IF function is used to return the color red if one or several fields are invalid. Otherwise, IF returns a blank value, which has no effect on the background color. The net effect is that the background color of the app is made red if one or several fields of the app are invalid.

Enabling a button only if all fields have been filled out

The Enabled property of a button determines if users can interact with the button. If a button should only be enabled if all fields of the app have been filled out, associate this formula with the Enabled property of the button:

The ISDEFINED function returns a logical array when its sole parameter is an array. TRUE elements in the array indicate that the fields have defined values, that is, have been filled out. Conversely, FALSE elements indicate that the fields have not been filled out.

Finally, the AND function returns TRUE only if all elements of the array are TRUE, otherwise it returns FALSE. The net effect is that AND returns TRUE only if all fields of the app have been filled out, prompting the Enabled property to only allow users to press the button once all fields have defined values.

Including all field values of the app in an email

The Body property of email report buttons allows the body of an email to be set through a formula. While email report buttons have built-in support for including field values, through the IncludedFields property, building a text string manually to include in the email body allows us more flexibility.

Consider this formula, which should be associated with the Body property of an email report button:

Above, the formula fragment App.Fields.LabelApp,Fields,Label returns a text array, made up of the labels of the fields of the app. The formula fragment App.Fields.ValueApp,Fields,Value also returns an array, this time made up of the values of the fields. Using &, the labels are joined together with the values, separated by a colon.

The resulting text array, where every element consists of a label, followed by a colon and a value, is converted into a single text string using the TEXTJOIN function. Its first parameter, NEWLINE()NEWLINE(), ensures that the array elements are separated from one another using line breaks.

Ranges versus this property

If the app only consists of the fields Field1, Field2 and Field3, these formulas are equivalent:

The second formula uses a range to create an array consisting of Field1, Field3 and all fields that appear between them, which in this case is only Field2.

The chief advantage of the Fields property, compared to a range, is that there is no need to update formulas when additional fields are added to the app. If Field4 were to be added to the form screen, the Field1:Field3Field1:Field3 range would have to be changed to Field1:Field4Field1:Field4 everywhere it is used.

By contrast, App.FieldsApp,Fields automatically includes Field4, and any other fields that are added.

Filtering fields

If you want to process only a subset of the fields returned from this property, use the FILTER function. It can base its decision on which fields to return on the property values of the fields.

This formula only returns visible fields:

Crucially, you can also filter on the names of the fields, using standard text functions. This formula only returns fields whose names include the text string "Required":

If you use a deliberate naming strategy for your fields, you can use FILTER in conjunction with this property to ensure that you only process a specific subset of fields.

Related properties

Use the Fields property of a form screen to access all fields of said form screen and the Fields property of a form group to access all fields of said form group.

The Items property returns not only fields, but also buttons and text boxes. From the point of view of the Items property, the Fields property returns only certain items, those that are fields. Use NumberFields, TextFields, SwitchFields, DateTimeFields, NumberDropDownFields and TextDropDownFields to only access certain fields.

Examples