--- schema_version: "1" id: b88e1e1dc7f34ede8eb6e3a169d998de1c4e24e7a494335b38e647202972a7f1 title: SalesMethodologyDef collection: legacydeveloper version: current locale: en-us portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/object_reference/sforce_api_objects_salesmethodologydef.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_salesmethodologydef.htm source_site: developer.salesforce.com content_type: documentation content_hash: d0ad94ab045a1d952e3eae5a9c3f6a4a57a7a27bed94ce1e299d130a486fef27 description: Represents the template of criteria for a sales methodology. This object is available in API version 67.0 and later. --- # SalesMethodologyDef Represents the template of criteria for a sales methodology. This object is available in API version 67.0 and later. ![Important](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note_important.png) #### Important Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations. ## Supported Calls describeSObjects(), query(), retrieve() ## Special Access Rules To access this object turn on the userHasSalesMethodologyEnabled, OrgPreferences, SalesMethodologyPref, and PipelineInspectorUser permissions. To read records, users must have the userHasSalesMethodologyEnabled permission. To create, edit, or delete records, users must have the CustomizeApplication user permission. ## Fields | Field | Details | | --- | --- | | Category | Type picklist Properties Filter, Group, Restricted picklist, Sort Description Required. Methodology categorization allows each object to add one methodology per record type and category. For example, an Opportunity with the Big Deal record type can have one Sales methodology and another Scorecard methodology. Possible values are: - Sales - Scorecard | | Description | Type string Properties Filter, Nillable, Sort Description Details about the sales methodology and its purpose. | | DeveloperName | Type string Properties Filter, Group, Sort Description The unique name of the sales methodology. The name: - must be 40 characters or fewer - must begin with a letter - can contain only underscores and alphanumeric characters - can't include spaces - can't end with an underscore - can't contain 2 consecutive underscores In managed packages, this field prevents naming conflicts on package installations. With this field, a developer can change the object's name in a managed package and the changes are reflected in a subscriber's organization. | | IsActive | Type boolean Properties Defaulted on create, Filter, Group, Sort Description Required. Indicates if the sales methodology is active (true) or not (false). The default value is false. | | Language | Type picklist Properties Filter, Group, Restricted picklist, Sort Description The combined language and locale ISO code, which controls the language of the sales methodology. | | MasterLabel | Type string Properties Filter, Group, Sort Description The label for the sales methodology. This display value is the internal label that doesn't get translated. | | ObjectType | Type picklist Properties Filter, Group, Restricted picklist, Sort Description For internal use only. Required. The type of object for which the sales methodology works. Possible values are: - Opportunity - Voice | | StandardPromptTemplate | Type string Properties Filter, Group, Nillable, Sort Description The standard prompt that can generate the criteria for the sales methodology when Agentforce is enabled. |