The column view option is a feature of Outline view only. This is why it is greyed out in other views. That makes sense, as most view expand in 2 dimensions where as an outline expands in one dimension (vertically on screen)
It is true that Attribute Browser view allows use of columns, but there it is implemented via different mechanism.
Also, Column view is not used for sorting but simply for giving a table-type one-screen display of one or more extra attributes. To group items on a map you could use $Sort (and $SortAlso) values applied to the container of the map (i.e., in outline view, the container holding all the map’s items). You can also use smart adornments.
See this recent thread, How are Tinderbox's map cards grouped by prototype?, for more explanation of how you can sort/group in maps. The thread also covers use of smart adornments.
Another approach is to make a new tab and use Attribute Browser view. There, you select you maps container as the scope of the view and choose $Category as the attribute of interest. Now you will see banner headings for each $Category value in use above a list of notes i=using that value: you can do a lot more.
In summary, remember, column view is only for Outline view. Also, insisting on only using one view is like buying a racing car and never getting out of first gear. All the views use the same underlying data, you are just seeing it visualised in different ways—ways that can help with a task that may be difficult/not possible in other views.