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).-
Adding some of the fields from the DB to NXT is already coded as shipped (only a couple of the fields needed were added) so this needs to be available as well.
If the thought is to use them more then we need to be able to filter by them.
Filtering by custom fields is available in Constituent and Gift lists right now, needs to be available for all types of lists.
We have an elaborate Moves Management process on the proposal tab in Database View. A few fields were changed to suit our needs. Moves Managers like this setup because they can attach their actions, media, and notes. We did not have to use the attributes/custom fields on this tab because everything was there in one proposal. The only issue was exporting, which we found a workaround for. Now that I'm trying to set things up in NXT in preparation for the “Unified View,” I'm noticing that not all the fields have transferred over to NXT. The Opportunities section doesn’t seem as robust as DBV. Our team doesn’t connect the gift details to the proposal since the gift is logged on the gift tab; therefore, that step didn't seem necessary. Plus, our two tables of data ended up in this section under "Gift Type" and "Likelihood". I’m very interested in knowing where the “Likelihood” data would come from in NXT, or is this a custom table-driven field created by each organization? I have attached a screenshot of our proposal tab in DBV. All fields in Opportunities and any attributes attached to them should be available in lists, exports, reports, filters, etc.
You can add custom fields to opportunities in web view, but why can't we output these into opportunities lists and filter by them! Custom fields are key to getting my organisation to step away from spreadsheet recording. They are ideal for organisation-specific data fields, such as which forecast this opportunity is recorded in, but not being able to out put custom fields in opportunities lists is a problem! You can't even use cons lists to output opportunities to work around
Still unable to filter Opportunity lists or do anything with customized fields which is hamstringing us as we need to be able to pull funding based on a custom field and cannot repurpose any of the built-in fields. PLEASE change this!!!
What's the point of having fields if you can't filter on them?
Very discouraging to see this initial idea is almost 6 years old. Makes me very doubtful it'll ever happen. I don't understand why custom fields are available on other list types but not Opportunity lists.
Please let us use all the fields! It's frustrating to enter records with the information we need to track, and then not be able to access that information in lists, reporting, etc.!
Please can this be implimented soon? It's a real difficulty for us.
When are custom fields available to filter in lists? We need this to track and report on specific opportunties.
My fundraisers would love it if we could filter/sort opportunities based on Constituent data, like location. And because we don't have access to Opportunity attributes in NXT, we can't even hack the system by adding the constituent region to an opportunity attribute. Just GIVE ME ALL THE FIELDS.
In our RE7 database, we've used proposal attributes (custom fields in NXT) to help flag budgeted proposals. However, looking up opportunities in NXT doesn't give you the option to filter by those custom fields or allow you to create an output column of custom fields. Either solution would go a long way towards helping with prospect review and keeping my team's fundraisers up to date.