Configure Custom Settings in Field Service Management

Custom configuration in NetSuite's Field Service Management (FSM) allows administrators to tailor account-specific setups by merging them with core functionalities. This capability is crucial for adapting the FSM platform to individual business needs, enabling seamless service delivery and enhanced management.

How Do Custom Configurations Work in FSM?

NetSuite’s Field Service Management operates on a two-level structure: Core Product Code and Configuration Code. The core product code, encapsulated within a NetSuite SuiteApp, governs fundamental FSM behaviors and is immutable by users. In contrast, the configuration code is user-accessible, allowing customizations via the Field Service Configuration record.

What Is a Custom Configuration?

The custom configuration, often known as the config file, is a JSON object representing the default account setup. Deployed initially with base settings, it enables rapid onboarding by showcasing tasks and content instantly in the mobile app. This customization covers about 90% of use cases, facilitating fast deployment.

Merging Core and Custom Configurations

Custom configurations are dynamically merged with core product settings during runtime. Only properties explicitly set in the custom config override the core settings, ensuring customizations don’t disrupt existing functionalities. For arrays, a complete override occurs, requiring intentional management to avoid loss of default behaviors.

Best Practices for Custom Configurations

• Limit Active Config Files: Ensure only one custom configuration file is active to prevent conflicts.
• Copy Before Modify: For significant changes, copy core configurations into custom setups. Remove unnecessary data post-modification.
• Test with Configuration Preview: Use the Configuration Preview feature to simulate runtime config outcomes, ensuring the desired operational effect.

Who This Affects

• Administrators: Setting up and managing FSM configurations
• Consultants: Advising on FSM implementations and customizations
• Developers: Writing custom configuration scripts

Key Takeaways

• FSM’s custom configurations allow tenant-specific customization by merging with core product settings.
• Only properties defined within custom configurations will replace core settings.
• Use Configuration Preview to anticipate runtime behavior before deployment.