Arrays in Field Service Management...

TL;DR Opening

Arrays in Field Service Management (FSM) configurations play a critical role in custom setups. Unlike objects that can be merged property-by-property, arrays completely replace their default values when overridden, which requires careful management by users.

How Do Arrays Function in FSM Configurations?

In the context of FSM configurations, arrays are defined as content enclosed in square brackets, such as filter and item. Unlike other configuration elements, when you override an array, the entire base array is replaced rather than merged. This distinction is essential for users to grasp to maintain the standard behavior of the FSM features.

What Happens When You Override an Array?

If you only wish to add elements to an array, it’s crucial to copy the entire array from the core configuration into your custom configuration. If you fail to do this, you'll inadvertently remove all default behaviors and values. Therefore, ensure that you always include the existing elements of the base array and then append your new values.

Merging Custom Configuration with Core Product

When the FSM product runs, it merges your custom configuration with the core product code. The core product code is integral to the FSM’s functionality, while the custom configuration allows specific customization tailored to each user's account.

Important Configuration Note

Users should ensure that only one custom configuration file is active at any given time, marking the others as inactive. This practice prevents potential conflicts and ensures that the primary custom setup is correctly applied.

Runtime Configuration Overview

During runtime, the configuration JSON merges with the core product code to determine how the FSM operates. If no custom JSON is defined, the FSM defaults to the core configuration behaviors. The Configuration Preview feature offers a method to visualize this runtime merging process, making it easier to understand how your configurations affect the FSM behavior.

Note: The behavior of the FSM product code can change based on the activated NetSuite features in the account.

Key Takeaways

Arrays in FSM configurations replace the entire base values when overridden instead of merging.
Always copy the complete base array for modifications to maintain its default behavior.
Only one active custom configuration file should be enabled to reduce conflicts.
The Configuration Preview feature allows users to visualize merged configurations effectively.

Source: This article is based on Oracle's official NetSuite documentation.

Frequently Asked Questions (4)

How are arrays managed differently from objects in Field Service Management configurations?

In Field Service Management configurations, arrays replace the entire default values when overridden, unlike objects which merge property-by-property. This requires careful management to maintain default behaviors.

What should I do if I want to add elements to an array in FSM configurations?

To add elements to an array, you should copy the entire array from the core configuration into your custom configuration and then append your new values. Failing to do this will remove all default behaviors and values.

Can I have multiple custom configuration files active simultaneously in FSM?

No, only one custom configuration file should be active at a time to prevent conflicts and ensure the primary custom setup is correctly applied.

How can I visualize how custom configurations merge with core product code in FSM?

You can use the Configuration Preview feature to visualize how custom configurations merge with the core product code during runtime, helping understand the impact on FSM behavior.

Arrays in Field Service Management Configurations