Why does the umbTable have an extra Name column by default?

Questions
1

In includeProperties, I don’t have the Name column.

<umb-table ng-if="tags"
           items="tags"
           item-properties="options.includeProperties"
           >
</umb-table>
$scope.options = {
    includeProperties: [
        { alias: "Tag", header: "Tag" },
        { alias: "ContentId", header: "Content Id" }
    ]
};

The image shows the 'Tags' section of a content management system, displaying a list of tags associated with "room (1)" and providing an option to add new tags. (Captioned by AI)
The image shows the 'Tags' section of a content management system, displaying a list of tags associated with "room (1)" and providing an option to add new tags. (Captioned by AI)1791×637 30.6 KB

Why does the umbTable have an extra column named “Name” by default? I don’t want this column to be displayed，Is the Name column necessary? How should I bind the data?

2

Name column is special in that it should render a link for your clickevent. (your use case here could be to open your related content ID for editing?)
Can you not just use Name for your tags? Semantically it’s the name of your tag ?

Think there is also an Icon property that you can assign too, so that you get well an icon :slight_smile:

Also bulk operations if allowed would add another column with checkboxes.

But I guess ultimately it’s because this is a umbTable and not just a table.. :slight_smile: and all backoffice umbTables have functionality dependant on a Name column?