1. Field Service Management
  2. Field Service Management Administration
  3. Field Service Management Configuration
  4. Field Service Configuration Reference
  5. Automatic Mapping of NetSuite Fields for an FSM Mobile Tab

Automatic Mapping of NetSuite Fields for an FSM Mobile Tab

Use the automap property to map Field Service Management (FSM) Mobile elements directly to fields on the associated NetSuite record without needing to define each field in article.map. When automap is set to true, FSM treats an element as mapped at runtime if its element ID exactly matches the internal ID of the corresponding NetSuite field.

By default, the automap property is not set to true for any FSM Mobile tab.

The property doesn't modify the configuration. Existing explicit mappings continue to apply and take precedence over automatically mapped elements.

How Automatic Mapping Works in FSM

FSM processes the configuration for an FSM Mobile tab with automap set to true as follows:

  1. Reviews the elements configured for the mobile tab.

  2. Checks whether each unmapped element ID matches a field ID on the record specified by article.record.

  3. Treats each element with a matching ID as mapped at runtime.

Requirements for Using the automap Property

Before you set automap to true, confirm the following:

  • Each element intended for automatic mapping corresponds to an existing NetSuite field.

  • Each element ID exactly matches the corresponding NetSuite field ID.

Important:

If an element ID doesn't match the corresponding NetSuite field ID, FSM can't map the element automatically. This mismatch can cause the request for the mobile tab to fail and prevent tasks from loading in FSM Mobile.

Automatic Field Mapping Example

In this example, the custrecord_details_text element ID exactly matches a field on the customrecord_details_form record. Field Service Management treats the element as mapped at runtime without requiring an entry in article.map.

            {
  "routes/mobile": {
    "details_form": {
      "label": "Details Form",
      "icon": "clipboard",
      "min": 1,
      "automap": true,
      "element": {
        "custrecord_details_text": {
          "type": "text",
          "label": "Enter Details"
        }
      },
      "article": {
        "record": "customrecord_details_form",
        "parent": "custrecord_details_task"
      }
    }
  }
}

Explicit Mapping for an Element with a Different ID

In this variation of the Details Form example, details doesn't match the internal ID of the corresponding NetSuite field. The article.map property maps details to custrecord_details_text. FSM uses this explicit mapping for details.

            {
  "routes/mobile": {
    "details_form": {
      "label": "Details Form",
      "icon": "clipboard",
      "min": 1,
      "automap": false,
      "element": {
        "details": {
          "type": "text",
          "label": "Enter Details"
        }
      },
      "article": {
        "record": "customrecord_details_form",
        "parent": "custrecord_details_task",
        "map": {
          "details": "custrecord_details_text"
        }
      }
    }
  }
}

Related Topics

General Notices