> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/collections/collection-view/table.md). # Table View When you want to display entities in a tabular layout within a collection, use the Table Collection View Kind. The table renders without a custom element — you only need to define which columns to show in the manifest. The Table Collection View renders items produced by a [Collection](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/collections/collection.md). The collection is responsible for fetching items through its [Collection Repository](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/collections/collection.md#collection-repository). The columns defined in `meta.columns` map to fields on your collection item model. In the example below, `status` and `creator` map to fields on `MyCollectionItemModel`. For details on defining the item model, see [Collection](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/collections/collection.md#item-model). The table kind always renders the following columns automatically: | Column | Description | | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | Always the first column. Renders the item icon and name. | | **Description** | Rendered only when at least one item in the collection has a description. | | *(manifest columns)* | Any columns defined in `meta.columns`, inserted after Name/Description. Values are rendered as strings by default, or via a [Value Summary](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/value-summary.md) when `valueType` is set. | | [**Entity Actions**](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/entity-actions.md) | Renders the item's Entity Actions menu. | ## Column options Each entry in `meta.columns` supports the following properties: | Property | Required | Description | | ----------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `label` | Yes | The column header text. | | `field` | Yes | The field name on the collection item model to read the value from. | | `valueType` | No | A [Value Type](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/value-type.md) key. When set, the column renders the value using the matching [Value Summary](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/value-summary.md) instead of a plain string. | Register the Table Collection View in the extension registry with the kind set to "table": ## Manifest {% code title="umbraco-package.json" %} ```json { "type": "collectionView", "kind": "table", "alias": "My.CollectionView.Table", "name": "My Table Collection View", "meta": { "columns": [ { "label": "Status", "field": "status", "valueType": "My.ValueType.Status" }, { "label": "Creator", "field": "creator" } ] }, "conditions": [ { "alias": "Umb.Condition.CollectionAlias", "match": "My.Collection" // Collection alias to display this collection view for } ] } ``` {% endcode %} In the example above, the `status` column uses a `valueType` to render its value through a registered Value Summary. The `creator` column renders its value as a plain string. {% content-ref url="/pages/C1juTytk62TLp9mcbbug" %} [Value Type](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/value-type.md) {% endcontent-ref %} {% content-ref url="/pages/G704guuPgcsb1WAYvrr8" %} [Value Summary](/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/value-summary.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.umbraco.com/umbraco-cms/extend-your-project/backoffice-extensions/extending-overview/extension-types/collections/collection-view/table.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.