FSM Mobile Event Map Field Components
The event map is the named set of values available for the current mobile event. Each item in the map creates an event-map field that can be referenced elsewhere in the mobile configuration.
|
Callout |
Description |
|---|---|
|
Event map field name |
It is a configuration-defined name and does not have to match a NetSuite field ID. |
|
Mapping definition |
Specifies how FSM obtains the event-map field value. A mapping definition can reference a field on the searched record, a field reached through a joined record, or a search formula. It can also provide a custom event-map field for use elsewhere in the mobile configuration. |
For an event sourced from a Task or Project Task, the values returned by that source's mapping form the event map. Use meaningful, unique event-map field names, and use the same name whenever you reference the value. When a mapping directly references a NetSuite field, use that field's ID as the event-map field name where practical. You are not constrained to the field ID: use a different name when it makes the configuration clearer or when you are defining a custom mapping.
Event Maps and Resource Article Maps in FSM Mobile
An event map provides context for the current event. Reference an event-map field as event.<event-map-field-name>.
A resource's article.map has a different role: it maps the fields for the NetSuite record displayed or edited by that resource. An element is the mobile control that displays, collects, or uses those mapped values.
The two maps can work together, but they are not interchangeable. For example, an event-map field can provide a default or filter value for a resource, the resource's article.map controls how that resource's record fields are loaded and saved.