FSM Mobile Element Validation Rules
This topic is intended for administrators and developers who configure element validation in Field Service Management (FSM) Mobile.
Configure validation properties for the intended values, including values supplied through defaults, mappings, and expressions. The following validation rules apply:
-
requiredchecks for a non-empty value. For a required table, at least one row is needed. Each row's child elements have their own rules. -
minandmaxset inclusive limits for numbers, dates, times, and date-times. -
A Number
steprequires a multiple of that increment, measured from zero. For example, withstep: 0.25,1.25is valid and1.30is not. Settingmindoesn't shift the numeric increment base. -
A Date
stepuses the configuredminas its base, or1970-01-01whenminis omitted. Forstep, dates use days. Times and date-times use seconds. For minute-based Time fields, usestep: 60and values with seconds set to00. -
precisioncontrols decimal entry and display. It is not a separate validation rule for values supplied by mappings or expressions. -
maxlengthsets a character limit for Text, Textarea, and HTML. It constrains editable entry, and resource-completion validation also checks preloaded text against it. Check values supplied by NetSuite defaults, mappings, and expressions. Loading a value doesn't automatically truncate it. In FSM Mobile, Save checks differ from resource-completion checks. Saving successfully doesn't establish that a value exceedingmaxlengthis valid. -
patternapplies a regular expression to a non-empty text value. Userequiredseparately when the field must also be completed. The supported types areemail,password,tel,text, andurl. -
The editable Email control has its own format check. Configure
patternwhen a format must also be checked during form validation. -
A Select value contains an option's
idandlabel, or an array of these objects for multiple selection. A bare option ID is not the documented value format.
Hiding, disabling, or making an element read-only doesn't automatically remove its validation requirements. If the element requires a value, ensure that the value can be supplied without user entry.
Element validation is separate from NetSuite validation during synchronization. A value accepted in FSM Mobile can still be rejected by record permissions, required NetSuite fields, scripts, or other account rules.
A record can save successfully but its resource can remain incomplete. For example, text returned from NetSuite that exceeds the element's maxlength fails resource-completion validation. If a required resource no longer has enough valid records, its tab shows the action-required asterisk again. The element itself doesn't have to be marked required for an over-length value to fail validation.
For Time and DateTime, a record passing Save validation in FSM Mobile doesn't establish that it satisfies every configured increment rule. Keep values aligned to the intended increment and check both saving and resource completion. The Time Save check measures increments from midnight, including when min is configured.