Custom Fields in Opportunity Lists

In the same vein of wanting to be able to filter on custom fields within proposal, we would also like to be able to choose these as columns on our custom lists so that we could sort by those fields.

  • Ryan Car
  • Mar 14 2016
  • Attach files
  • Suzie Capps commented
    March 13, 2023 13:14

    We also need this to be able to use Opportunities properly.

  • Teddi Taylor commented
    June 21, 2018 15:32

    I agree.

  • Drew Matthews commented
    February 06, 2018 23:07

    Yes - need Likelihood/rating in Opportunity Lists.

  • Brooke Donovan commented
    November 01, 2017 16:19

    There is no ability to even see the Custom Attributes on an Opportunity in any list which is currently rendering them useless. Please add!

  • Matthew Nareff commented
    October 24, 2017 12:46

    Because some fields don't exist in NXT that are in the database for Opportunities it is really important to be able to filter by custom fields.  In the suggestion about adding a couple of fields that are in the database- https://community.blackbaud.com/products/raisersedgenxt/ideas- one of the suggestions made by Blackbaud was to use custom fields more.-

    Jonathon Leeke commented
    July 26, 2016 18:17
     

    We do have to be careful about bloating the default fields in NXT.  In some cases, if fields are not commonly used, it may make sense to use custom fields.  Is that an option for any of these - Rating, Instrument, or Type of Gift?  Can you explain how these fields add value for your users?  What are they doing with that data?  

    Would other field names make sense...for example maybe Rating would be better named as "Likelihood"?  

    Renamed fields do not carry over to NXT with their custom name - only the default name is used (ie. Instrument would show instead of Format).-

    If the thought is to use them more then we need to be able to filter by them. 

     

     

  • Bill Connors commented
    March 24, 2017 16:58

    Custom fields in proposals/opportunities are needed in Lists as both columns and filters.