S
Shannon Mostert
Custom objects hold a lot of useful data. For example, bookings have status, date booked and more, and children have their own fields and a relationship to the contact. Today it's hard to segment or view contacts using the fields on their associated custom objects.
Example: contacts in a specific lifecycle stage who have children with August birthdays and who have attended a specific type of class.
What we'd like, in each of these places:
  1. Custom object and contact views: When I add a filter, I can choose fields from the object I'm viewing and from any associated object (contacts, bookings, children and so on). I can also add those associated fields as columns. For example, in Contacts I can show booking fields, and in Bookings I can show contact fields.
  2. Lists: After choosing a starting object (for example, contacts), I can filter on fields from any associated custom object, to build more targeted lists.
  3. Automations: When setting up triggers and conditions, I can use fields from associated custom objects, not only the object that triggered the automation.
If there are other places where associations should show up, we'd welcome those too.