Configuring Field Service Mobile Table Elements
Use Field Service Management (FSM) Mobile table elements to define collections of row values. A top-level table element defines the row structure, and its child elements define the columns and values stored in each row. This topic explains how to configure table elements, how table values are stored, and how FSM Mobile handles parent references.
Table Definition
Use a top-level table element followed by its direct child column elements. Set each child element's parent property to the table's name. The table element is the parent and defines the row structure. Each child element defines a value stored in each row. Don't assign parent to a non-table element or another table element.
The following example defines a materials table with description and quantity columns:
[
{
"name": "materials",
"type": "table",
"label": "Materials"
},
{
"name": "description",
"parent": "materials",
"type": "text",
"label": "Description"
},
{
"name": "quantity",
"parent": "materials",
"type": "number",
"label": "Quantity",
"min": 0,
"step": 1
}
]
Stored Table Value
The stored value for a table element is an array of row objects. For example:
{
"materials": [
{
"description": "Filter",
"quantity": 2
}
]
}
Parent Validation Behavior
Field Service Mobile finds child elements by matching the parent string. During normalization, Field Service Mobile doesn't separately reject a missing parent or a parent that doesn't reference a table element. However, only a table element uses matching child elements as columns and iterates the values in each row.
A missing or non-table parent isn't supported and might prevent the element from rendering or validating in the intended table context.