Cutomise contact, list and segment table (columns, sort etc)
It would be good to be able to customise list view - which columns display, in what order (swap columns around) and be able to sort on different columns.
-
Yoshiki Kuraki commented
+1 too.
-
Anonymous commented
Same!
-
Chaplain TIG commented
Yes please!
-
joe commented
+1
-
[Deleted User] commented
In too !
Hope this will be here soon as it really wears to arrive and don't see others columns you configured had hard time to get some data on. -
Sam Dilon commented
I'm in for this. I really need to sort by date and phone number. Not having the phone number column is a big issue for me. Let's make this a priority yea?
-
Minoo Razavi commented
This is an extremely helpful feature to have and It must be fairly easy to implement. If not custom sort, at least the ability to sort by the existing columns in order of alphabet or date as applicable...
-
Anonymous commented
a must
-
Selena commented
Yes please!
-
Anonymous commented
I have to say, it is rather frustrating not being able to customise the contact list, seeing a lot of empty columns that are no use to me at all.
-
Christen commented
Please add column selection and more robust table management.
-
Anonymous commented
please include this in your next update
-
Erik ayers commented
There are two columns that don't even show information. Not being able to determine what columns show in main contact view is an oversight.
-
Waqar commented
This is a must have thing, currently, we have more than 5000 contacts and we have to go through each of them manually to view custom fields.
This should be done at the earliest.
-
Casey commented
+1, we need this to work just like Salesforce list views. The most interesting data is in our custom fields!
-
Philippe RAE commented
This is clearly something that is needed.
Autopilot store a lot of interesting data but makes it impossible to mine.
We havea custom field that is used to create a segment.
We can see the contacts in the segment but need to click on each and every one of them 9we have 2,600) to see the value of the custom field.
That is silly and pretty much defeats the purpose of it all.
What is the point of segmenting over a field if you can't see the field in the segment?