Preparing for FSM Configuration Assessment

Collect the configuration files, HTTP Archive (HAR) files, and account details needed for an assessment of your Field Service Management (FSM) configuration. The result is a set of files and context that a technical consultant, partner, or internal resource can use to assess the account's configuration and observed behavior.

Required Assessment Inputs

Collect the following inputs from the same NetSuite account and installed FSM version.

Input	Required Information
Current unmerged configuration	The complete custom JSON from the active configuration record's Editor, before merging with product defaults.
Clean base-product Preview	The full Preview output containing account-specific product defaults without customer overrides, apart from the Preview setting.
HAR files	At least one HAR file from FSM Mobile or the Schedule Board, depending on the assessment scope. If both applications are in scope, collect at least one HAR file from each. Capture the session with the normal custom configuration active.
Account context	Account ID, production or sandbox account, exact sandbox identifier if applicable, and installed FSM version.

HAR files help the assessor understand requests, responses, and timings from the session you want assessed. Configuration alone cannot establish faster loading, request counts, or data savings.

Warning:

Configuration and HAR files can contain credentials, personal information, and business data. Follow your organization's data-handling requirements before sharing files, including with an artificial intelligence (AI) tool.

To prepare for FSM configuration assessment:

1. Preserve the current unmerged configuration.

   Go to Field Service > Administration > Configuration and identify the active configuration record. Copy the complete JSON from the Editor and save it as a separate file. Keep this file unchanged throughout the assessment.

2. Record the account details.

   Record the NetSuite account ID, account type (production or sandbox), exact sandbox identifier if applicable, and installed FSM version.

   Also record useful context, such as the active configuration record name or ID, collection date and time, time zone, NetSuite release, affected roles, and intended business outcomes.

3. Obtain the clean base-product Preview.

   Have the authorized account owner follow Configuration Preview.

   Important:

   This method temporarily changes active behavior. Use a controlled window when the change will not affect ongoing work.

   An inactive Preview-only record can still include active custom settings. The JSON entered in the Editor is not the required Preview output.

   1. Preserve the original configuration and activation state before making changes.

   2. Save a separate configuration record named Base Product Config containing only {"config":{"preview":true}}.

   3. Inactivate all other configuration records.

   4. Activate the Base Product Config record.

   5. Open the active Base Product Config record in edit mode.

      Preview shows the standard product configuration.

   6. Save the full Preview output as a separate file.

   7. On the configuration list, check the Inactive box for the Base Product Config record.

   8. Clear the Inactive box for each configuration record that was active before collecting Preview. Leave previously inactive records inactive.

   9. Click Submit.

   10. Reopen the configuration page and verify that the Base Product Config record is inactive. Confirm that the original configuration records match the activation state recorded before collecting Preview.

4. Collect HAR files.

   Collect at least one HAR file for FSM Mobile or the Schedule Board, depending on what you want assessed. Start with a full initial load for the relevant technician or dispatcher, with the normal custom configuration active. Follow Capturing FSM Performance Data for collection instructions.

   For each capture, record the application, user role, capture date and time, time zone, and the actions performed. Describe the behavior you want assessed.

5. (Optional) Collect supporting information.

   Include relevant FSM Help references or details of account-specific customizations that may help the assessor interpret the files. Identify the applicable FSM version and the source of the information.

6. Confirm the inputs and provide them for assessment.

   Confirm that the files match the recorded account details and identify any missing inputs before providing the files for assessment.

   Provide the files and account details to the technical consultant, partner, or internal resource carrying out the assessment. State what you want assessed, such as configuration behavior or loading performance.

Keep the original collected files unchanged so they remain a record of the configuration and session provided for assessment.

General Notices