FSM Record Model Settings
This topic is intended for administrators and developers who configure record model properties and defaults.
Each record model has its own top-level property in the FSM configuration JSON, such as "models/asset", "models/case", or "models/task". Use the exact configuration ID listed in the Model Index.
Within a model's root object, prototype contains instance settings such as map, defaults, and supported model-specific properties. Some settings belong directly inside the root object. Examples include the asset duplicate comparison settings uniqueFormula and uniqueTemplate. Each model entry identifies where its documented settings belong.
For configuration placement, merging, Preview, and activation, see FSM Configuration. For map and search syntax, see FSM Searches and Field Mapping.
This topic includes the following sections:
Defaults and Inheritance
The defaults property supplies attributes omitted when a new model is created. Existing record values are read from NetSuite. Certain models also apply defaults during form initialization or validation. Their individual entries describe that behavior. A Boolean default on those paths can replace an existing value, including a value of false.
Models can inherit another model's field mappings and behavior. A change to a base model can therefore affect several record types. An individual model can supply its own mapping or default in place of the inherited value. Check each affected model's effective configuration. Derived models can supply different mappings and defaults.
Each model entry begins with a standard default JSON fragment showing its mappings, defaults, and the model settings covered here, including relevant inherited values. These are reference fragments, not replacement configurations. Executable methods and callbacks are omitted. Properties that vary with enabled features and account-formatted values are explained beside the fragments because their effective values vary by account.
The model tables identify useful standard mappings and explicit defaults. The tables don't list every field supported by each NetSuite record. A visible implementation property is not necessarily a customer configuration option. Retain record identity, relationship mappings, and specialized behavior when making a supported change.
Model methods, event callbacks, synchronization functions, and processing functions are not portable configuration recipes. A new FSM Mobile resource with the same record type or copied JSON can have different fulfillment, transformation, inventory, and related-record behavior. For article configuration, see FSM Mobile Resource Properties Reference. For supported operations, see the relevant feature topic.
Custom Forms for Record Creation
For a NetSuite record created through a record model, prototype.defaults.customform supplies the internal ID of the custom form used for creation. This applies to Journal Entry, Opportunity, Quote, and Sales Order models as well as other models that create records through the shared record-creation path.
|
Property |
Purpose |
Standard Default |
Effect and Dependencies |
|---|---|---|---|
|
|
Selects the NetSuite custom form used when creating a record through this model. |
No form ID is assigned by the standard Journal Entry, Opportunity, Quote, or Sales Order defaults. |
Uses the specified form when the new model's attributes don't already supply |
For example, the following customization fragment supplies a Sales Order form default. Merge the fragment into the existing configuration. The inherited Sales Order defaults remain in effect.
Replace 123 with the applicable Sales Order form's internal ID.
{
"models/salesorder": {
"prototype": {
"defaults": {
"customform": 123
}
}
}
}
Use the same prototype.defaults.customform location within models/journal, models/opportunity, or models/quote for the corresponding record type. This default applies to creation through that model. It doesn't select the form displayed when opening an existing NetSuite record. An FSM Mobile resource's form setting and article defaults have their own configuration. For resource form settings and article defaults, see FSM Mobile Resource Properties Reference.