You are here:
Considerations for Customizing Opportunity Teams
If you customize opportunity teams, review considerations related to custom fields, team member information, and validation rule and Apex trigger support.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
Custom Fields and Picklists
| Maximum Custom Fields | You can create up to 50 custom fields for an opportunity team. |
| Custom Field Visibility | When editing team members, users see custom fields, even if you don't add the fields to the Add Opportunity Team Members multiline page layout. |
| Deleting Custom Fields | If you delete a custom field, filters based on the custom field are also deleted. The results of assignment or escalation rules that rely on the custom field's data can change. |
| Default Values in Custom Fields | If you include a default value for a custom field, the field appears blank to Lightning Experience users while they're adding opportunity team members. If users don't enter a value, the default value appears on the record after they save. |
| Custom Picklists | Mass Reassign Opportunity Teams doesn't support custom picklists. |
Team Member Information Display
| Displaying Team Member Information on a Parent Page | To display opportunity team member information on a parent page, link the team member and the parent. For example, to display team member information on the related account detail page, add a custom lookup field to the multiline editor. Label it Account to the Opportunity Team. Then set this field to the parent account for each opportunity team member. |
| Lookups to Team Members Not Supported | You can't create a lookup from an object, such as an account, to an opportunity team member. |
| Sorting in Related List | You can customize the sort order of the related list in the Opportunity Team Member page layout. However, if a user sorts the related list by a different column, the list keeps that sort order even after the page is refreshed. |
Validation Rule, Flow, and Apex Trigger Support
| Lightning Experience Support | Validation rules, flows, and Apex triggers are applied when Lightning Experience users add their default team to an opportunity using the Add action on the related list. However, they're not applied when Lightning Experience users select the personal settings option to add their default team to opportunities automatically. |
| Salesforce Classic Support | Validation rules, flows, and Apex triggers aren't applied when Salesforce Classic users add default opportunity teams via any method. |
| Ownership Change | When an opportunity team member is removed during an opportunity ownership change, Apex triggers are bypassed. |
Did this article solve your issue?
Let us know so we can improve!
