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

Reading and Saving FSM Field Values

Note:

This topic is intended for administrators and developers who configure how field mappings read and save values.

FSM field mappings define how search values are read and which NetSuite fields receive saved values.

This topic includes the following sections:

Returning Mapped Values or Native Search Results

The objectify property controls whether standard search retrieval converts results using the map. Its default is true. In configuration, this property is useful for resolved searches supplying report or email template data.

Setting

Returned Data

Effect of an Object Map

true, or omitted from the effective search definition

Values read and converted using the map.

The map's property names become the returned object's property names.

false

Native NetSuite search results.

Map values select search columns. Map property names don't rename the native results.

For example, "duration": "durationdecimal" produces a mapped property named duration when objectification is enabled. With objectify: false, a native-result template instead references the search column durationdecimal.

The native-results path skips FSM's mapped-value conversions and mapped duplicate-row merging. Sorting and summary operations defined on the search columns still apply. The consumer must accept native search results. These results cannot replace the mapped objects expected by FSM Mobile articles or Select options.

Omitting the property from custom JSON retains any inherited value. Check the effective definition before changing it.

For standard report settings and matching XML examples, see Search Results and objectify and Field Names in Report Templates in FSM Service Report Configuration.

Reading and Saving Different Fields

A mapping can read a search column and save to a different record field. Place the read mapping before | and the write mapping after it.

Mapping

Read Behavior

Save Behavior

"title"

Read the title search column.

Write the title record field.

"case.internalid|supportcase"

Read the linked case ID through the search join.

Write the task's supportcase field.

"status#|"

Read the displayed status text.

Don't write a destination field.

"|message"

Don't supply a search-column value.

Write the task's message field when a value is supplied.

Without a pipe, a plain field mapping uses the same name for reading and writing. A formula mapping without an explicit write destination is read-only.

For example, this resource article map reads and saves notes through the task's message field and displays status without writing it:

            {
  "notes": "message",
  "statusLabel": "status#|"
}

The resource's elements would be named notes and statusLabel. If an element is renamed, update its article mapping as well.

A read-only mapping and an element's readonly property have different purposes. The mapping controls the NetSuite write destination. The element property controls editing in the FSM Mobile interface. If a displayed value should not be edited, configure the element accordingly.

Important:

Mapping display text back to a List/Record field can depend on its available labels. Prefer internal IDs for saved selections. Use ! only when a field must be set again: forcing an otherwise unchanged write can trigger field-change processing.

Additional Information

Related Topics

General Notices