FSM Asset Model Customer Selection
This topic is intended for administrators and developers who configure customer eligibility for assets.
The asset's owner is the singular customer attribute, mapped by prototype.map.customer to custrecord_nx_asset_customer. The plural customers settings control which customers can be selected for work against that asset. Permitting another customer for service work doesn't change the owner stored on the asset.
The prototype.map.customers mapping supplies the first result. It can read a field or formula, or supply a literal Boolean value. The prototype.customers property defines a fallback search. The following table describes how mapped results control customer choices and use of the fallback search.
|
Mapped Result |
Customer Choices |
Fallback Search Used? |
|---|---|---|
|
Literal |
Leaves the native Customer field's normal choices available, without the Asset-based restriction. It doesn't mean 'use the owner field' or 'enable a field mapping.' |
No. |
|
Literal |
No permitted Customer candidates. |
No. |
|
A nonempty ID string, such as |
Only the customers identified by that string. |
No. |
|
An array of IDs, such as |
Only the listed customers. An empty array, |
No, including for an empty array. |
|
A blank string, |
The customers returned by |
Yes. |
With the standard configuration, an asset owned by customer 42 produces the mapped result "42". That result restricts the Customer choices to its owner, so the fallback search is not used. Mapping customers to a Customer multiselect instead allows the customers listed in that field to be used for service work.
If prototype.map.customers is set to "", FSM uses prototype.customers. The standard search also finds the owner: in ${ asset.customer || 0 }, asset is the selected asset and asset.customer is its owner ID. The tag inserts that ID into the search filter, or 0 when no owner ID is present. A custom search can find a different permitted relationship, such as service providers linked to the Asset.
The search collection's array: true combines its results into an ID list, such as [42, 73]. FSM then uses those IDs to retrieve the Customer labels for the selector. Return IDs from this lookup, rather than Customer display objects.
Normal NetSuite access and field restrictions still apply when true removes the Asset-based filter. These settings define permitted candidates. An existing selection can be retained when a form first opens. For selection, sourcing, and saved-value behavior, see FSM Customer and Asset Selection.