Please consider making it possible to sort a contact list on Associated Company.
I can confirm that Hubspot have done nothing about this, its poor that nearly every other column is sortable
Can’t figure out why “Associated With” can’t be sorted. It is already being listed in the view. For this little thing, paying for Pro for workflow is not justifiable. It is indeed very helpful for monthly review and presentation.
Hello @shawnlin,
I was able to find this idea created in our ideas forum here
This idea status still in submitted but my recommendation would be please like the idea and leave your comment there as our product team is constantly checking for updates, this will ensure they are aware of our customer’s need and any updates to that idea you will be able to receive a notification.
Kindly,
Pam
Hi Pam,
I’ve left message in the post you indicated. Do you have a timeline when that idea will be reviewed?
Hi @shawnlin
We don’t have a timeline currently, if you left a comment in the idea, you will receive an email once is updated by our team.
Kindly,
Pam
I have a question regarding the workaround that @Phil_Vallender describes.
How do you solve the issue that the workflow doesn’t update the contact property “company name” if the associated company of said contact is changed (instead of initially entered) or simply the name of a company gets update?
It sounds HubSpot suggest workflows when simple tasks can’t be achieved from the front end. I don’t think is appropiate to close this idea because a workflow is suggested as a workaround and only benefit those customers who licence the Pro version.
I had a very negative experience using a ‘simple’ workflows that HubSpot support setup for me and went totally wrong. Since then I’m walking away from ‘the workflow magic wand’. Workflows are usually setup by HubSpot support or advance software users and I think this is not suitanable for your customers on a long term when employees leave the organisation and those automation magically change information on the front end due to complex workflows to fix simple issues. Is this a strategy to quietly upsell to HubSpot Pro maybe?
It’s very surprising that this was suggested nearly four years ago and there still isn’t an easy, accessible solution. We attempted to create a redundant Company Name property in addition to the Associated Company so that we could sort by it, but that’s only opened up more opportunities for human error, more work to enter those properties when creating new contacts, more headaches…
Sorting by Associated Company should be standard. It’s shocking that it isn’t.
It is puzzling indeed why this fundamental column is not sortable. However, there is a relatively straight forward workaround.
1. Create a custom property under the Contact object with data type Single-line text. Let’s assume this property is called Custom_Company_Sortable.
2. Export all your contacts to a CSV. You only need to export Contact Name, Contact Email and Company Name as illustrated below:
3. Open the CSV, it should look like the following:
4. Delete the following columns; Contact ID, First Name, Last Name and Company ID. Rename Company name to Custom_Company_Sortable (the name of the custom property created in Step 1).
The updated CSV should look like this:
5. Import the updated CSV back into Hubspot. Make sure not to overwrite the existing contact details. The import will only update Custom_Company_Sortable.
6. Now you can sort by company using the Custom_Company_Sortable column. In my case the custom property is called SS_SORT. I have removed the names and emails from my screenshot for privacy purposes. However, as you can see the custom field is sortable. In my case I am sorting by website.
Test the import with a few contacts to make sure it works before updating the whole database.
Hope this helps.
Thanks for sharing this workaround, @SS_PD!
This is a joke, I am regreting my moving from Pipedrive. This needs to be fixed, I am paying in excess of €30k for this and I can’t view my contacts based on their organisation!
December 2024 and this is STILL a problem.
We really need this!