FSM Mobile Quote Customization Dependencies and Limits

For additional business data, prefer adding body fields or columns to the Items table using supported elements and mappings. Preserve the existing fields, defaults, validation, read-only rules, and relationship mappings. These settings support quote saving, task associations, and signed-quote conversion.

This topic includes the following sections:

• Rates and Price Levels

• FSM Mobile Quote Item Options and Task Context

Customize the existing standard quote resource. The transaction base, estimate mappings, and specialized server synchronization work together. This combination saves estimates, applies requested relationships, converts existing signed quotes, and reloads saved values.

Warning:

Don't directly duplicate the Quote JSON under a different resource ID as a way to retain Quote behavior. The same record type or article.extend: "models/transaction" supplies neither the Quote-specific case application nor signed-quote conversion. A similar screen and a successful local save don't establish equivalent NetSuite outcomes.

Preserve the standard protections and dependencies when applying an override:

• The article mapping makes quotes with the Processed status read-only. Line mappings make lines belonging to another task or project task read-only. Enabling resource actions doesn't remove those restrictions. A quote containing read-only lines cannot be deleted through the standard tab.

• Keep existing item lines returned by the standard mapping in the submitted data. The transaction update can remove saved lines omitted from that data. Hiding a line and excluding it from the submitted mapping have different consequences.

• Retain the body and line relationship mappings, the saved signature mapping, and the read-only Total and Status controls. These controls display saved results and don't confirm that the transaction workflow is complete.

• Apply to current Job uses the task's project and case where present. Project association writes the native job field when Project Management is enabled and entity otherwise. Case application updates custevent_nx_case_transaction.

• Signing during initial creation doesn't invoke the standard sales order conversion branch. An update to an existing quote containing a signature does, including a previously saved signature submitted again. Don't treat a signature on another tab as the Quote conversion control.

Warning:

Preserve every required Quote line mapping when replacing article.map.items. An incomplete editable line collection can remove saved lines. For more information, see Mapping Table Values to Sublists.

The standard Quote tab has no currency selector or inventory-assignment controls. Quote conversion and the direct Sales Order tab are separate paths. Don't transfer the Sales Order tab's fulfillment settings to Quote. For that workflow, see FSM Mobile Sales Order Management.

Rates and Price Levels

The standard Quote tab has no rate-entry field or price-level selector. You should retain NetSuite pricing and avoid adding controls for rate entry or price-level selection, including Custom pricing. Preserve the standard saved Amount and read-only Total mappings.

Warning:

Adding pricing controls can override NetSuite-sourced pricing, including customer-specific pricing. Writable rate fields can submit blank or incorrect rates when adding or editing lines, interfering with rate sourcing or changing transaction amounts. Don't add these controls as routine Quote-tab customizations.

For the related pricing cautions, see Configuring FSM Mobile Sales Order Management. That topic distinguishes standard price-level choices that you can configure from unsupported Custom pricing and direct rate entry on the Sales Order tab.

FSM Mobile Quote Item Options and Task Context

For conditional configuration changes:

• If you override inventory.element.orderable.options, complete the following:

  • Preserve each required option's id, label, description, and min.

  • Keep the Quote expressions consistent with that list.

  • Check the Order tab, which also uses it.

• If you change task mappings or defaults for quote creation, retain the context listed in the following table. Check quotes created after the change and existing quotes.

The following table lists the task context used by Quote configuration.

Context	Quote Usage
event.customer, event.date	Customer and date during estimate creation, plus custbody_nx_customer.
event.crmtask, event.projecttask	Estimate custbody_nx_task or custbody_nx_projecttask during creation, with line custcol_nx_task or custcol_nx_projecttask.
event.asset	custcol_nx_asset during line creation.
event.internalid	Task-specific selection and line ownership checks.
event.job, event.supportcase	Additional quote selection and Apply to current Job processing. Both must match for the additional selection. The standard project task map has no case context.
event.email	Initial value for the Emails field. The standard task map reads the case email. Supply an available address in the event context, including for project tasks.
event.subsidiary	Estimate initialization during creation when Multi-Subsidiary Customer is enabled.

For search and map syntax, see FSM Searches and Field Mapping. For task-context template tags and FSM Mobile expressions, see FSM Expressions and Template Tags.

Additional Information

• FSM Mobile Sales Order Management
• FSM Field Mapping Reference
• FSM Mobile Resource Properties Reference
• FSM Transaction Base Model Reference

Related Topics

• Configuring FSM Mobile Quote Management
• FSM Mobile Quote Configuration Reference

General Notices