Introduction to Data Views, Tables and Saved Views

A data view is the table you work in almost everywhere in BackOps. Crew, collaborators, tasks, areas, expenses, procurements, your organization's events, locations and databases all appear in the same component, with the same toolbar, so once you have learned it on one page you know it on all of them.

Why Data Views Matter

Event work is list work. On any given day someone is scanning the crew list for who still has no call time, someone else is checking which tasks are overdue for one department, and a producer wants the same task list as a timeline before a production meeting. When each list behaves differently, every one of those questions starts with relearning the screen.

Data views make the list itself the tool. The same controls filter, group, sort, total and chart whatever is in front of you, and the arrangement you build can be saved and shared, so the "overdue tasks by department" view is built once and opened by everyone who needs it.

How Data Views Work

Every data view has three layers.

flowchart TB
    R["Records on the page (crew, tasks, events...)"] --> L["Layout: Table, List, Calendar, Gantt or Kanban"]
    L --> T["Toolbar: search, filter, group, properties, view settings"]
    T --> V["Saved views: named tabs above the table"]

Layouts decide how the records are drawn. Table is always available; each page adds the layouts that fit its records, such as Calendar and Gantt for tasks. See layouts, filters and calculations.

The toolbar narrows and arranges what you see: a quick search, filters, grouping, which properties are shown, and the View settings menu for everything else, including charts and colors.

Saved views capture all of that as a named tab, either shared with everyone on the event or organization or private to you. See saved views.

On pages built for it, you can also select rows and change a field on all of them in one action. See bulk editing records.