Heather I see the option in the constituent lists but I am unclear how to use it? I think many people asked for this because Fundraisers often use lists whereas Data people use queries and have more advanced experience for using them. The opportunity lists in particular are used by Fundraisers who need to be able to use one list for example and filter it in different ways while using it. We encourage this so we don't end up with a trillion lists over time in the database. If there are some new best practices and knowledgebase on using this query feature, and it is available on all list types, sharing that to our teams would be helpful.
We appreciate how diligent BB is being with these requests!
Thanks, Heather. Query filters aren't an option for opportunity lists, so prioritizing the addition of operators like "is not" and "is blank" would be most impactful in that area.
Thank you everyone for the feedback and discussion.
We reviewed the original request behind this idea and the primary need was the ability to support exclusion and "NOT" scenarios when building and refining Lists. With the introduction of Query filters in NXT Lists, users can now exclude records that match selected criteria by leveraging Query-based filtering. This delivers the core capability requested in this idea, which is why we have marked it as Shipped.
It's also important to note that this idea was created before web view Query capabilities were available. Since then, the platform has evolved significantly. Query-backed Lists now provide a flexible way to support a broad range of exclusion scenarios without requiring us to introduce a dedicated NOT operator for every filter type.
As a result, we believe the original, overarching request has been addressed. Rather than keeping this idea open indefinitely to represent a growing collection of individual filtering needs, our goal is to focus on specific remaining use cases. If there is a scenario that cannot be accomplished with the current Query-backed filtering experience, please submit a new idea describing that workflow and desired outcome so we can evaluate and prioritize it independently.
Examples of scenarios raised throughout this idea where your needs may still not be met include:
Excluding specific constituent codes when creating mailing and email lists.
Identifying opportunities without an assigned solicitor. This one is planned as part of future list enhancement work.
Excluding gifts associated with a specific event, campaign, fund, or other criteria from broader fundraising results.
Thank you to everyone who voted, provided examples, and helped us better understand how customers use Lists in their day-to-day work.
Heather I see the option in the constituent lists but I am unclear how to use it? I think many people asked for this because Fundraisers often use lists whereas Data people use queries and have more advanced experience for using them. The opportunity lists in particular are used by Fundraisers who need to be able to use one list for example and filter it in different ways while using it. We encourage this so we don't end up with a trillion lists over time in the database. If there are some new best practices and knowledgebase on using this query feature, and it is available on all list types, sharing that to our teams would be helpful.
We appreciate how diligent BB is being with these requests!
Thanks, Heather. Query filters aren't an option for opportunity lists, so prioritizing the addition of operators like "is not" and "is blank" would be most impactful in that area.
Thank you everyone for the feedback and discussion.
We reviewed the original request behind this idea and the primary need was the ability to support exclusion and "NOT" scenarios when building and refining Lists. With the introduction of Query filters in NXT Lists, users can now exclude records that match selected criteria by leveraging Query-based filtering. This delivers the core capability requested in this idea, which is why we have marked it as Shipped.
It's also important to note that this idea was created before web view Query capabilities were available. Since then, the platform has evolved significantly. Query-backed Lists now provide a flexible way to support a broad range of exclusion scenarios without requiring us to introduce a dedicated NOT operator for every filter type.
As a result, we believe the original, overarching request has been addressed. Rather than keeping this idea open indefinitely to represent a growing collection of individual filtering needs, our goal is to focus on specific remaining use cases. If there is a scenario that cannot be accomplished with the current Query-backed filtering experience, please submit a new idea describing that workflow and desired outcome so we can evaluate and prioritize it independently.
Examples of scenarios raised throughout this idea where your needs may still not be met include:
Excluding specific constituent codes when creating mailing and email lists.
Identifying opportunities without an assigned solicitor. This one is planned as part of future list enhancement work.
Excluding gifts associated with a specific event, campaign, fund, or other criteria from broader fundraising results.
Thank you to everyone who voted, provided examples, and helped us better understand how customers use Lists in their day-to-day work.
Yes and should be available on all list types including Opportunities to filter by Assigned Solicitor is blank.