As a recurring HubSpot user, I’m requesting the ability to create a single custom property (e.g., a dropdown or radio button) that can be used across multiple object types—specifically, Contacts, Deals, and Tickets—and displayed in their respective list views (index pages). Right now, I understand that HubSpot properties are object-specific. If I want to track the same information in Contacts and Deals (e.g., “Engagement Stage,” “Lead Type,” or a client tier dropdown), I have to duplicate the property for each object. That means managing multiple versions of the same data, training users to enter it in two places, and introducing unnecessary complexity. Here’s why this change would be so valuable: Efficiency: One shared property saves time and admin overhead. It allows our team to align data across records without switching between tabs or duplicating fields. Data Integrity: No more inconsistencies caused by updating only one object’s version of the property. One source of truth. Usability: Users can see, sort, and update that property directly from both the Contact and Deal dashboards (or Tickets too), making their workflows much smoother. Reporting Clarity: Shared properties across views would also enhance custom reporting, filtering, and segmentation. I understand that fields like “Contact > Deal” are currently limited to displaying associations, not shared, editable values. But introducing cross-object editable properties—at least optionally—would be a game changer for scaling and aligning CRM data. If there’s any workaround or beta functionality in the works, I’d love to know. Otherwise, I hope this makes it onto the product team’s radar. Thanks for all the great work, Michael
... Mostrar más