FSM Opportunity Model Reference
This reference is intended for administrators and developers who work with Opportunity model mappings and inherited transaction behavior.
This model represents opportunity and derives from Transaction. Its baseline enables entity synchronization and adapts the transaction map for Opportunity searches. It uses a different ID formula based on lineitem. Project writes to job when Project Management is enabled and otherwise to entity. Unsupported inherited search columns for created-from data, email, contact, and purchase order are removed. Defaults remain inherited and empty.
Standard default structure (JSON fragment):
{
"models/opportunity": {
"prototype": {
"record": "opportunity",
"map": {
"id": "*formulatext:case when {lineitem} is null then {internalid} end|internalid",
"type": "formulatext:nvl({recordtype}, lower({type}))",
"entity": "entity",
"customer": "custbody_nx_customer",
"asset": "custbody_nx_asset",
"case": "custbody_nx_case",
"task": "custbody_nx_task",
"status": "status",
"date": "trandate",
"paymentmethod": "paymentmethod"
},
"defaults": {},
"syncentity": true,
"inventory": false
}
}
}
For the meaning of the inherited syncentity and inventory properties and guidance on changing these properties, see Transaction Mappings and Processing Properties.
The prototype.map.project mapping is "|job" with Project Management and "|entity" without it. The inherited prototype.map.projecttask is "custbody_nx_projecttask" when Project Management is enabled. These conditional entries are omitted from the fragment.
Use prototype.defaults.customform to supply the form for opportunities created through this model. For information about this setting, see Custom Forms for Record Creation. Use the Opportunity record and FSM view definitions for the supported integration. Replacing the adaptations with the generic Transaction map can introduce invalid Opportunity search columns.