Multi view
A Multi view reads one dataset and offers it as several presentations: a list, a calendar, a kanban board and a gantt chart. The user switches between them without the data being fetched again.
Which presentations are available is decided by which fields you map. Map a start field and the calendar appears; map a bucket field and the kanban board appears; map a gantt start and the gantt chart appears. There is no separate switch to turn each one on.
Cell editing in the list is off by default, and List: allow editing turns it on. It does not govern dragging: moving an event in the calendar or a card between kanban lanes changes the object either way, as far as the user’s M-Files permissions allow.
Each user can reorder, minimise and colour the kanban lanes for themselves. A user with the Manage common views vault right can also save a layout as the common default that everyone starts from.
Multi View
How the Multi View sources and renders its data: the data source plus the per-mode field mappings (list / calendar / kanban / gantt).
Title
The title shown above the view. Default: no title.
Height
The height of the component in pixels. Default: sized to its content.
Time slot length (minutes)
Calendar mode: the length in minutes of each time slot in the week/day views. Default: 30.
Data source
Where the Multi View gets its data. The dataset is de-typed server-side and rendered as a list, calendar, kanban or gantt.
Default mode
Which view mode the Multi View shows first. Default: List.
ListCalendarKanbanGantt
List: allow editing
Lets users edit cells in the list mode - text, numbers, dates, yes/no and lookups, several cells at once, saved in one batch. Off by default: an Edit button on a list is an invitation to change data, and not every list is meant as one. M-Files permissions apply either way; this only decides whether the list offers editing at all. Dragging events and cards in the calendar and kanban modes is not affected. Default: no.
Auto-refresh interval (seconds)
Automatically re-check for changed objects every N seconds and merge them in without a full reload. 0 (default) disables auto-refresh. Values below 30 are treated as 30 to avoid hammering the vault. Search sources only; deleted objects are not removed until the view is reloaded. Default: 0.
Order by field
Optional. The dataset column key to order the rows by. Orders the kanban cards within each lane and the gantt bars (and the underlying data for the other modes). Dates and numbers sort naturally.
Order descending
Sort the order-by field from highest to lowest (newest date / largest number / Z–A) instead of ascending. Default: no.
List: group field
Optional. Groups the list-mode rows under a header for each value of this column, like the classic List View's grouping. Users can also change this on the fly via the list's Group-by option.
Icon field
Optional. A lookup column whose value icons are shown on each list row, kanban card and gantt bar (a multi-select lookup shows several icons). When empty, the object's class or type icon is used.
Colour by field
Optional. A dataset column whose value colours the items in every view — calendar events, kanban cards and gantt bars — with one shared colour per distinct value (deterministic, so a value gets the same colour in each view), plus a legend below each view to show and toggle the values. e.g. colour opportunities by product.
Summary fields
Optional. Number columns to total at the bottom of the list and on each kanban lane. Each entry picks a dataset column key and whether to show the sum or the average.
Calendar: start field
The dataset column key to use as the event start date. Setting this enables the calendar mode.
Calendar: end field
Optional. The dataset column key to use as the event end date. Defaults to the start date.
Calendar: title field
Optional. The dataset column key to use as the event title. Defaults to the object's name.
Kanban: bucket field
The dataset column key whose value groups rows into kanban lanes. Setting this enables the kanban mode.
Kanban: card title field
Optional. The dataset column key to use as the card title. Defaults to the object's name.
Kanban: card detail fields
Optional. Dataset column keys shown as extra 'label: value' lines under each card title (e.g. owner, value, due date). The title and bucket columns are skipped automatically.
Gantt: start field
The dataset column key for each bar's start date. Setting this enables the gantt mode (otherwise the calendar start field is used).
Gantt: end field
Optional. The dataset column key for each bar's end date. Defaults to the start (a milestone).
Gantt: label field
Optional. The dataset column key shown as each bar's label. Defaults to the object's name.
Gantt: group field
Optional. The dataset column key whose value groups bars into gantt swimlanes.
Gantt: dependency field
Optional. A lookup / relationship column whose values are each task's predecessors; the gantt draws a finish-to-start arrow from each predecessor's bar to this one.
Generated from CtrlPortals 3.26.9.53.
Related
Section titled “Related”- Configuration overview
- About CtrlPortals — how modules sit inside segments