Compatibility of NetSuite Features...

TL;DR

NetSuite features can have different compatibility levels with Field Service Management (FSM). Understanding these relationships is crucial for Administrators to ensure proper functionality without causing errors.

Compatibility Levels

NetSuite categorizes feature compatibility with FSM into four main classifications:

Required: The feature must be enabled for FSM to work correctly.
Optional: FSM operates independently of this feature; it can be enabled or disabled without affecting FSM's functionality.
Incompatible: This feature, if enabled, will result in errors in FSM or prevent functionality.
Not Tested: The feature's behavior with FSM is unknown as it hasn't been tested.

Support Levels

Support levels indicate how the behavior of NetSuite features applies to FSM:

Full: The behavior applies fully to all FSM features.
Partial: Only some behaviors affect FSM features.
None: No integration; the feature does not impact FSM.
Not Applicable: The feature does not interact with FSM.

Company Features Compatibility

The following table outlines various company features and their compatibility support levels with FSM:

Feature	Compatibility	Support Level
Subsidiaries	Optional	Full
Departments	Optional	Full
Locations	Optional	Full
Classes	Optional	Full
Projects	Required	Full
Project Management	Optional	Full
Planned work	Optional	Full
Job Costing and Project Budgeting	Optional	Partial
Advanced Project Profitability	Not tested	None
Activity Codes	Optional	None
Advanced Project Budgets	Not tested	None
Multiple Units of Measure	Optional	None
Use Deletion Reason	Optional	None
Multi-Subsidiary Customer	Optional	Full
Advanced Numbering	Optional	None
Resource Allocation	Optional	Partial
Multi-Language	Optional	None
Multiple Currencies	Optional	Full
Inline Editing	Optional	Full
File Cabinet	Required	Full
Enhanced File Security	Optional	None
IP Address Rules	Not tested	Not applicable
Mobile Push Notification	Not tested	None

This information is crucial for ensuring that your configurations do not conflict, leading to a smoother operational experience with FSM.

Who This Affects

Administrators: Responsible for enabling and configuring features.
Developers: May need to consider feature compatibility during development.
Field Service Management Users: Could experience functionality issues based on feature configurations.

Key Takeaways

Understanding feature compatibility with Field Service Management is key to avoiding errors.
Different levels of support indicate how features will behave in relation to FSM.
Keep track of which features are required, optional, or incompatible when configuring your setup.

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

Frequently Asked Questions (4)

Does feature compatibility in NetSuite 2026.1 apply to all NetSuite editions?

The article does not specify whether feature compatibility with Field Service Management in NetSuite 2026.1 applies to all editions. It's advisable to consult detailed release notes or NetSuite support for specific edition applicability.

What happens if I enable an 'Incompatible' feature with Field Service Management?

Enabling an 'Incompatible' feature with Field Service Management will lead to errors, causing unexpected behavior. It's crucial to avoid activating these features to maintain system stability.

How can I determine if a feature is required for FSM in NetSuite 2026.1?

Features marked as 'Required' are essential for the proper functioning of Field Service Management, meaning enabling them is mandatory to ensure smooth operations.

What should I do if a feature is marked as 'Not Tested' with FSM?

If a feature is marked as 'Not Tested' with FSM, proceed with caution as its functionality may be inconsistent. Consider testing thoroughly in a sandbox environment before enabling it in production.

Compatibility of NetSuite Features with Field Service