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" or "OR" 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.

Thank you to everyone who voted, provided examples, and helped us better understand how customers use Lists in their day-to-day work.

Please merge with idea https://renxt.ideas.aha.io/ideas/RENXT-I-3520 - these are the same.

I would love to see all of the choices that are available on database side - especially those that are "blank" or "not one of." 

Some lists don't have "one of" as well.