Tags
A tag that can be put on cards, such as Revenue. Create each tag once and put it on cards with tag_refs of cards. Tags are matched by name, so a tag that already exists in the target is reused. Without color the tag gets a color of the palette.
Files in the package
List every file of this entity in resource_files of the manifest, with "resource": "tags". An entity can have any number of files. See Bundle format.
[
{
"resource": "tags",
"path": "resources/tags.json"
}
]Fields
| Field | Type | Required | Description |
|---|---|---|---|
external_id | string (ExternalId) | Yes | Your own identifier of the record, for example k-mrr, unique within the resource across all of its files and case sensitive. Other records refer to this one by it.Constraints: 1–512 characters. |
name | string | Yes | Name of the tag, for example Revenue. Up to 255 characters; names are distinct without regard to case.Constraints: 1–255 characters. Rule: Unique without regard to case. |
color | #RRGGBB? | No | Tag color. It is replaced with the nearest color of the option palette; an omitted color gets a default one. Constraints: the nearest color of the target palette is used. |
References
Referenced by
- Cards:
tag_refs
Show on the entity map
Example
A record of this entity:
{
"external_id": "t-revenue",
"name": "Revenue",
"color": "#66bb6a"
}Rules
- The value of name must be unique without regard to case.
Related entities
Cards
Check after the import
After the import, the records of this entity can be checked on Tags › Retrieve list of tags.
JSON Schema
tags.json
