I agree it would be great to have available all fields that are not one to many. My boss would love to be able to see their primary education class of as an example. Also seems like there are several duplicate discovery topics on this subject matter - wonder if they could be merged so we can better use our votes.

I agree. There is no reason all one to one fields should not be available in QL.

I agree completely. I just tried to create a list of donors who attended an event, using the query we had previously created for the invitation. It is almost impossible. The only name fields that are in the query list are the salutation and full name - so the list is sorted on First Name!
Also, it would be good to be able just select names for inclusion, rather than have to select only for deletion.
It's really cumbersome and disappointing.

This full name field for participants being fn ln and sorting that way exists in regular queries - not just query lists. Have you filed or voted for that suggestion yet?

I do not agree that all fields should be available. You can not put in all that information and still have it function as a query list!!!

Do you know you can make a query list and then pull the results (people) into a regular query and get all that info you want? You will get the one-to-many problem with duplicate rows you already get but get to add many other fields.

My question is, why are people not taking the query list to export or reports to get what they want?

@Melissa Graves - we do not use the query list to export or put in reports precisely because you still have the one to many problem and query has so little real functionality that it is almost useless. And export is pretty much useless also. To do anything that is very useful you have to use crystal reports and those take way too long to create unless you have staff with time on their hands. We do not have people sitting around with nothing to do here - lol! Or perhaps we need to do more complex functions than other non-profits....we have many, many thousands of constituents of various types and the way that attributes and constituency codes are set up and function in RE is way too rigid to use effectively.

Kerry - I do not know what you are talking about. Query and reports always eliminate the one to many problem.

Have you used any other system besides RE - Rigid is hardly what I would call RE. Try eTapestry or Sage fundraising 50!!

If it is not working for you have a custom database designed for you.

At a minimum, having the primary and alternate addressee and salutation fields along with email address fields for the constituent and contacts (org records) available would be most helpful to those reviewing a mail list or e-blast list without one having to export to Excel. Once additions/deletions made by reviewers then one could take the final query list in mail to generate letters/envs, prepare the csv mail house export, tag records, etc.

Absolutely!!! Query List is great in theory, but we include Const ID to all mailings, so it has proven to be useless for us at this point. Please, please, please add some flexibility to the columns we can access, particularly all address, phone numbers & emails, attributes, and constituent IDs. I build my queries in the regular query section, then idealy would pull a bunch of queries together to narrow it all down instead of fumbling with ands and ors, just eliminate groups of folks and bam, have a list with all of the constituents I want, then be able to choose the columns of information I want to see. Please make this happen! Thank you!

Constituent ID is a must for Query List

We are adding more fields to Query List in 2013, however it won't be all fields; I'd like to hear more about what the most common requests are and why so we can make the best choices. We have heard Constituent ID loud and clear - what else, and why? Feel free to email me as well, jennifer.mercer@blackbaud.com

Top fields would be able to add which addressee/salutations get displayed (primary addressee/salutation or user defined one)! Other fields would be nice gift dates & fund list for first gift, last gift, recent gift (I know we can see them individually, but not as part of the results of the query list),

It would be wonderful if Export could be eliminated altogether and incorporated into Query. Query has become so much more functional over the years, I don't use Export as often anymore. I would like to be able to select the specific contact type. Also, maybe I am catching these comments after it was done, but Constituent ID is available in Query output.

Absolutely agree with everyone comments. Query List is a great concept. Development needs to see contact names for businesses. We also need to be able to sort by last name or sort by any field we choose.

Jennifer S. - You can sort by any column you have including name. If you choose the proper user options for your name display - it will sort by last name, first name.

I really need to see the contacts of the organization and it I could select only certain contact types that would be great. If not we can pull in reverse and show the names of everyone - but need to see who they work for. It would be nice to see which query they came from (to help identify why they are on the list)

You should at least be able to pull the output fields from the source query. Sort order should also carry over from the query. Without these I have to search through my query to find the people I want to remove then search through the list to find where they ended up when sorted by "name"

At the very least sort key should be included.