Field Service Configurations: Core...

NetSuite Field Service Management (FSM) utilizes a dual-layer configuration system to offer robust features alongside customizable options. This ensures a tailored, efficient implementation for each customer's unique requirements.

What Are the Two Levels of FSM Configuration?

Field Service Management separates its functionality into two primary layers:

Core Product Code: This pertains to the fundamental, non-modifiable behavior of the FSM system, installed as a SuiteApp with identifiers prefixed by "Field Service".
Configuration Code: This is user-accessible and modifiable, allowing customization through the Field Service Configuration record.

Core Product Configuration

This configuration, developed solely by the FSM product team, operates uniquely per account, adapting automatically to individual NetSuite settings.

Custom Configuration

The custom configuration, or config file, is stored as a JSON object and allows integration with the core product features. Each account deploys with a base configuration for quick functionality bootstrap, covering common requirements.

How Do Core and Custom Configurations Merge?

FSM merges configurations at runtime, integrating user-specified JSON changes with core code. Users should ensure only one active custom configuration file exists to prevent conflicts.

Merging Objects and Arrays

Objects (element, article) merge on a property-by-property basis, allowing precise overrides.
Arrays (filter, item) completely replace, rather than merge, the default values. Copying the entire core array is essential before adding custom values.

Configuration Runtime Management

Users can preview their runtime configuration within accounts, which overlays custom JSON onto the core product.

Note: In absence of a custom JSON file, FSM defaults to core functionality.

Who This Affects

Administrators: Require understanding of configuration merging for managing custom setups.
Developers: Must ensure proper JSON formatting for effective customizations.
Consultants: Guide clients in utilizing base configurations efficiently.

Key Takeaways

FSM employs a dual-layer configuration for tailored deployments.
Core codes are immutable, while custom configurations are flexible.
Mismanagement of array merging can result in loss of default behaviors.
Configuration Preview helps visualize runtime setups in real-time.

Frequently Asked Questions (4)

How can I customize the Field Service Management configuration in NetSuite?

You customize the Field Service Management (FSM) by modifying the Configuration Code. Create a custom configuration file under Field Service > Administration > Configuration, where you can define and adjust settings to meet specific customer requirements.

What is the impact of modifying arrays in the FSM custom configuration?

When you override an array in the FSM custom configuration, it replaces the entire base array. This means you'll lose all default behavior unless you copy the whole base array from the core configuration and then add your changes.

How do FSM core and custom configurations interact at runtime?

At runtime, the custom configuration JSON merges with the core product code. The core code runs by default, but the custom JSON can override it for specified sections. Without a custom JSON, FSM operates based on core product behavior.

How can I enable the Configuration Preview feature in NetSuite FSM?

To enable Configuration Preview, go to Field Service > Administration > Configuration, and in the JSON field, use {'config': {'preview': true}} to turn the feature on. Save the configuration page to apply the setting.

Field Service Configurations: Core and Custom Setup