1. Field Service Management
  2. FSM Configuration
  3. FSM Configuration Reference
  4. FSM Searches and Field Mapping
  5. FSM Field Mapping Reference
  6. Automatic FSM Field Mapping

Automatic FSM Field Mapping

Note:

This topic is intended for administrators and developers who configure automatic field mapping for resources in Field Service Management (FSM) Mobile.

Automap generates missing article mappings for a resource's top-level elements that carry values. It uses the element name and type, or the element's explicit map property.

For an example of mapping an element with a different name, see Mapping an Element with a Different Name.

Resource Configuration

Automap Behavior

form is supplied and automap is omitted.

Enabled. This includes "form": {}.

form is supplied and automap is false.

Disabled.

form is omitted and automap is omitted or false.

Disabled.

automap is true.

Enabled for the resource's eligible elements.

When enabled, Automap uses the following precedence for each eligible element:

  1. Keep the matching entry already defined in article.map.

  2. If that entry is absent, use the element's map property when supplied.

  3. Otherwise, generate a mapping from the element's name and type.

For example, a Text element normally maps to the field with the same name. A Select uses an ID-and-label object mapping. Its multiple property determines whether the selected value is an object or an array. File and Image elements use mappings that include the selected file ID and its address.

An element's map property is used through Automap. If Automap is disabled, define the required mapping in article.map. Automap doesn't infer the child-field mappings needed to save a Table to a NetSuite sublist.

Mapping an Element with a Different Name

The following fragment shows an element named notes mapped to the task's message field:

            {
  "automap": true,
  "article": {
    "record": "task",
    "filters": ["internalid", "anyof", "${event.internalid}"]
  },
  "element": {
    "notes": {
      "type": "textarea",
      "label": "Task Notes",
      "map": "message"
    }
  }
}

This example is a resource fragment for a CRM Task event. Automap creates the notes entry in article.map from the element's mapping. An explicit article.map.notes would take precedence over that element mapping.

Important:

Automap generates mappings. It doesn't check that the target field exists or is searchable. Use valid fields for article.record. Give a display-only element an appropriate explicit mapping or exclude it from automatic field mapping. An invalid generated search column can prevent the resource from loading.

For information about form loading and generated element properties, see FSM Mobile Element Reference. Search mappings supply record data. Form-generated initial values and element validation are separate considerations.

Additional Information

Related Topics

General Notices