FSM Record Model Mappings
This topic is intended for administrators and developers who define mappings between model attributes and NetSuite fields.
A mapping associates a model attribute, such as customer, with a NetSuite field or calculated search value. It can define the value read and the destination for writes separately. Existing FSM code continues to use the same attribute name after its mapping changes. The defaults property supplies an omitted initial value. The map connects the attribute to stored data.
For the effects of mapping changes, see Effects of Mapping Changes.
Effects of Mapping Changes
The following table summarizes the purposes and effects of mapping changes.
|
Change |
Purpose |
Effect |
|---|---|---|
|
Add an attribute |
Make an additional existing field available to a template, rule, or operation using that model. |
Model reads can include the extra field. The intended operation must consume the attribute to produce the required business outcome. Adding a mapping doesn't itself create a NetSuite field or an FSM Mobile element. |
|
Remap an existing attribute |
Point an existing FSM attribute to another compatible field for a supported account-specific requirement. |
Existing code continues using the attribute name but reads, and potentially writes, a different field. Related formulas and processing don't automatically adapt. |
|
Change a calculated mapping |
Adjust a documented calculation consumed by an existing feature. |
Changes the value supplied to that feature. Asset automatic naming and customer eligibility are examples of deliberate mapping customization. Use their specific configuration guidance. |
Adding an entry can expand the search columns used to load the model, even when no operation uses the new value. Retain standard identity, relationship, and transaction-line mappings because existing processing depends on these mappings.
Clearing or removing a mapping is not a general way to turn off behavior. Configuration null removes the entry during merging. Some read and write paths can then treat the attribute name as a native field ID. A blank mapping has different effects. Follow the exact documented instructions for any deliberate blank or removal.
The following fragment illustrates where a model mapping override belongs. Merge it into the existing custom configuration. It is not a replacement configuration.
{
"models/asset": {
"prototype": {
"map": {
"autoname": ""
}
}
}
}
Here, models/asset identifies the model, prototype contains its instance settings, and map.autoname identifies the mapping being changed. For this setting's effect and naming-specific guidance, see FSM Asset Model Reference.