Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    To clarify you question, are you asking if you can add the Related To field from Task to the related lists of activities on an Opportunity? If so, there's no need. The Related To field simply limits the WhatID field of activities to appropriate object. By the nature of the functionality, if the activity is displayed in the Opportunity related list, it is related to opportunities. Commented Jun 17, 2015 at 12:26
  • I just need to display Related To field in opportunity's related list named OPEN ACTIVITIES. Commented Jun 17, 2015 at 12:29
  • My point above is that even if you could (which you cannot, since that value is not stored as a field or data) it would display "Opportunity" in the related list of an Opportunity. It is redundnant. Commented Jun 17, 2015 at 12:31
  • 1
    I got your point what you trying to say (it is related to opportunity that is why it is redundant)....So, Why we need to add that field under the Opportunity page layout.....Right ? Commented Jun 17, 2015 at 12:41
  • 1
    The actual stored value is the ID of the related opportunity. You can add "Related To" to the related list, but it will simply display the name of the related record. If you want "Opportunity" to display, then you'll need to create a formula that evaluates the ID of the lookup into a text string. Commented Jun 17, 2015 at 12:46