Space boards
Places a board in a space. A board can be placed in several spaces without being copied; each record is one placement. Mark one placement of a board as primary (if none is, the app picks one). A space shows its boards one under another in the order of their records.
A record of this entity needs records of other entities in the package: Boards; Spaces.
Files in the package
List every file of this entity in resource_files of the manifest, with "resource": "space_boards". An entity can have any number of files. See Bundle format.
[
{
"resource": "space_boards",
"path": "resources/space_boards.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. |
board_ref | Ref<boards> refers to Boards | Yes | The board that is placed. Give the external_id of a boards record. |
space_ref | Ref<spaces> refers to Spaces | Yes | The space that shows the board. Give the external_id of a spaces record. |
primary | boolean | No | Whether this is the main placement of the board. When no placement of a board is primary, its first placement in the order of the records becomes primary, as the target does. Default: Rule: At most one main placement per board. |
References
Show on the entity map
Example
A record of this entity:
{
"external_id": "sb-kpi",
"space_ref": "s-kpi",
"board_ref": "b-kpi",
"primary": true
}Rules
- The combination of space_ref, board_ref must be unique.
- Among the records with the same board_ref, at most 1 can have primary = true.
Related entities
Boards, Spaces
Check after the import
After the import, the records of this entity can be checked on Space Boards › Get list of boards.
JSON Schema
space_boards.json
