Column-Level Filtering

The use case that makes this earn its place is scoping a question. A stakeholder says they think there was a data problem with leads last week. You go to contacts or deals, filter down, pull in create date, lifecycle stage, lead status, and a couple of attribution fields, then eyeball it to decide whether there is a real problem or one bad record skewing the read. The old path made you go through the gear, then edit columns, then the modal, before you could even start.

The honest caveat is that column management in views is still slow. The right rail is great for adding one column. If you are removing six and adding seven, you are clicking one at a time, and the column modal is the faster path even though nobody loves it. There is also a keyboard shortcut for table settings that fires for some people and not others.

The real news is that there is a filters team inside HubSpot now, heading into a sprint with work expected before Unbound, including association filtering on associated records. What stuck from that conversation is how much complexity sits under a request that looks obvious from the outside. Once associations enter the picture you have to decide whether the user picks the property or the association first, whether a property like create date appears once or once per associated record, and how labels multiply every version of it.