Merging Core Product and Custom Configuration
At runtime, Field Service Management (FSM) merges the core product configuration with the custom configuration. The custom configuration can override or extend default FSM behavior.
For background on these layers, see Core Product Configuration and Custom Configuration.
Keep only one custom configuration file active. Mark all other configuration records inactive.
Configuration Merge Behavior
The merge behavior differs for objects and arrays.
Objects
In JavaScript Object Notation (JSON), braces ({ }) enclose an object and its properties. Objects such as element, article, or map are merged property by property. Only the properties in your custom configuration override the corresponding core product configuration properties.
Copy only the properties you want to change into your custom configuration. This helps future product updates apply correctly and makes your customizations easier to identify.
Arrays
In JSON, square brackets ([ ]) enclose an array. Arrays such as filter and item are not merged. A custom array replaces the entire base array, even when the custom array contains only one new value. Copy the complete base array from the core configuration and then add your changes.
Configuration at Runtime
The core product code always runs. Without custom JSON, FSM uses the core product behavior. When custom JSON exists, FSM merges it with the core product configuration at runtime.
The Configuration Preview feature lets you view the runtime configuration in your account. For more information, see Field Service Management Configuration Preview.