Add demographic options to lists in RE NXT
The columns choices in RE NXT are not very useful, I still need to go to RE database view to make most lists to get the info needed. All demographic information should be column choices at the very least.
-
Cathi Christopher
- Mar 6 2019
- Reviewed: Voting Open
-
Oct 11, 2022
Admin response
We updated the original title of "Add all field options available in RE database view to lists in RE NXT" to reflect the original description which was target at demographics.
We see lots of great suggestions in comments for columns and filters that would help users get more out of lists. In order for us to prioritize and deliver the columns and filters with the largest impact first for our customers, please vote for the specific ideas in the community that represent those columns and filters.
[Since the votes and comments for this idea seem to reflect more than just demographic fields, we intend to mark this specific idea as "Will not ship", and will use votes for ideas targeted at individual sets of filters or columns.]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1218
Related ideas
Yes to all fields to be available in NXT please.
The information contained in the Education column needs to be separated out. One filter for Major, another filter for Grad Year, etc.
The lack of address fields and many others is a gigantic weakness in Lists and prevents using RE data effectivley. It should have been there from the beginning.
It would be helpful to include Primary Addressee and Primary Salutation for exports!
From the bio 2 tab. It would be good to see the ethnicities table which we currently use as nationality.
It would be essential to my workflow to have both the "Target" or ask amount field as well as "child" or "student" fields as columns in Lists.
We should also be able to include or exclude null values
The lists in NXT are seriously lacking. We need all fields available in NXT!
We need maiden name available. Am I just missing it?
Yes, to including all fields from db view to be available in web view, otherwise we cannot do our work! Thanks.
I also agree with adding all RE fields as column options in NXT. We have set up users in NXT who do not have rights for RE. The users for the Schools are not able to run a constituent list which can be used for a mail merge.
We need ALL fields! We can't go NXT exclusively without all of the field from database view. This is major struggle. It's disappointing that many things are still not available in NXT after years of usage. I get tired of saying "we can't do this in NXT." I don't understand the issue but i'm not a programmer either.
A "county" field needs to be added. Our organization is comprised of 6 regional offices and most of our appeals, communications and all of our major gift prospecting are targeted by county.
All fields from database view would be very helpful
Though all fields need to be added As Columns and Filters, here are ones missing that have stopped us froThough all fields need to be added As Columns and Filters, here are ones missing that have stopped us from using Lists: Count of Consecutive gifts ; Fund List ; Salutations and Addressees ; Constituent and Gift Lists Separate First, Middle, Last Name for Sorting ; Fund Split Amount to Gift List ; Fund ID in Gift List ; All Email Types; All Phone Types; All Name Formats
Another vote for ALL fields from DB view to be available in RENXT. We are in the process of implementing RENXT and I am disappointed withthe limitations in the List function.
We REALLY need the "county" field to be able to function in NXT with our state wide organization!
Please add a 'county' field.
Why wouldn't ALL fields from database view be available in NXT? If you want us to use NXT exclusively, make it work as well as the database side.
In order for us to prioritize and delivery the columns and filters with the largest impact first for our customers please vote for the specific ideas in the community that represent those columns and filters.
Does this mean we're to make new ideas to be voted on for the columns we want?