stacks Working with Databooks

Databooks are your consolidated data source with related tables. You can import data using APIs or upload Excel files, with data quality validation on import.

lightbulb Why Databooks

Databooks solve these problems:

Problem Databook Solution
Reference data scattered across spreadsheets Centralised tables with defined structure
No validation - typos and bad data get in Typed columns, validation lists, and constraints
No version control - who changed what? Automatic version history with user and timestamp
No access control - everyone can edit everything Permissions at databook, table, or row level
Manual data relationships - copy/paste between files Cross-table lookups maintain referential integrity

stacks What is a Databook?

A Databook is a container for one or more related tables. Each table has:

  • Columns with defined data types (text, number, date, boolean, list)
  • Constraints that validate data on entry
  • Permissions that control who can view or edit
  • Version history that tracks all changes

When to Use a Databook

Use Case Example
Reference data Cost centres, department codes, GL account mappings
Configuration Report parameters, threshold values, business rules
Manual input Budget adjustments, forecast overrides, manual journal entries
Hierarchies Org structures, chart of accounts roll-ups, product taxonomies
Note: Databooks are designed for reference data and manageable datasets. For high-volume transactional data, use your database or data warehouse and connect via API.

table_chart How to Create Tables

Option A: Start with a Blank Table

  1. Navigate to Databooks

    Go to Clarity > Databooks. Select an existing Databook or click New Databook.

  2. Add a table

    Click Add Table. Enter a descriptive name (for example, "Cost Centres" or "GL Mappings").

  3. Define columns

    Click Add Column for each field. Specify column name, data type, required yes/no, and optional default value.

  4. Enter data

    Click any cell to enter data. Use Tab to move across columns and Enter to move down rows. New rows are added automatically.

  5. Save

    Click Save or press Ctrl + S.

Option B: Import from File

  1. Start import

    From inside a Databook, click Add Table > Import from File.

  2. Upload file

    Drag a CSV or Excel file into the upload area. The wizard previews the first 20 rows.

  3. Map columns

    The wizard auto-detects column names and data types. Review and correct mismatches, rename columns, change types, or skip columns.

  4. Import

    Click Import. The table is created and populated in one step.

[Screenshot placeholder: Import wizard showing column mapping]
Import wizard showing column mapping.
Tip: Before importing, clean your source file: remove blank rows, ensure headers are in the first row, and use consistent date formats (YYYY-MM-DD recommended).

rule How to Set Up Data Constraints

Constraints prevent invalid data from entering your tables.

Data Types

Type Accepts Example
Text Any string "Marketing", "ACC-4010"
Number Integers or decimals 42, 1500.75
Date Calendar dates 2026-03-09
Boolean True / False true, false
List One value from a predefined set "Active", "Inactive", "Archived"

Validation Lists

Restrict a column to predefined values:

  1. Open column settings

    Click the column header, then select Column Settings.

  2. Set type to List

    Set data type to List.

  3. Enter allowed values

    Enter one value per line.

  4. Save

    Users now select from a dropdown instead of entering free text.

Cross-Table Lookups

Link a column to values in another table (like a foreign key):

  1. Open constraint settings

    Click column header, then Column Settings > Constraint.

  2. Select lookup

    Choose Lookup from another table.

  3. Choose source

    Select source Databook, table, and column.

  4. Save

    The column now accepts only values that exist in the source table.

Warning: Changing a column's data type after data exists may cause validation errors. Review the impact preview before confirming.

account_tree How to Create Hierarchies

Hierarchies define parent-child relationships within a table (for example, org chart, chart of accounts, product categories).

How It Works

A hierarchy uses two columns:

  • Node column - unique identifier for each row (for example, department code)
  • Parent column - lookup to the node column, indicating the parent row

Rows with empty parent values are root nodes.

Setup Steps

  1. Create a node column

    Create a column with unique values (for example, "Department Code").

  2. Add a parent column

    Create a parent column and set constraint to Lookup - same table - node column.

  3. Populate parent values

    Select parent for each row. Leave root nodes blank.

  4. Switch to hierarchy view

    Click View > Hierarchy to display the tree structure.

[Screenshot placeholder: Databook in hierarchy tree view]
Databook in hierarchy tree view.

Working with Hierarchies

Action How
Expand/collapse branch Click arrow icon next to parent
Move a node Change the parent column value
Add a child Add row and set parent to desired node
View flat Click View > Table
Export with levels Export includes a "Level" column showing depth
Note: Circular references (A parent of B, B parent of A) are automatically detected and blocked.

upload_file How to Import and Update Data

Update Modes

Mode Behaviour Use When
Append Adds new rows only; existing rows unchanged Adding new items to an existing list
Update Matches by key column; updates changed values; adds new rows Refreshing attributes on existing records
Replace Deletes all existing rows; imports new data Full refresh from source system

Running an Update

  1. Open the table

    Open the Databook table to update.

  2. Start update import

    Click Import > Update Existing Table.

  3. Upload file

    Upload CSV or Excel file.

  4. Select mode

    Select Append, Update, or Replace.

  5. Select key column (Update mode)

    Select the matching key column.

  6. Review preview

    Review rows to add, update, and delete.

  7. Apply

    Click Apply.

[Screenshot placeholder: Update wizard with change preview]
Update wizard with change preview.
Warning: Replace mode deletes all existing data before importing. Always verify the file and preview before confirming.
Tip: For recurring imports, ask your administrator about scheduled imports via API.

shield How to Configure Security

Permission Levels

Level View Edit Manage
Viewer Yes No No
Editor Yes Yes No
Owner Yes Yes Yes

Setting Permissions

  1. Open Databook

    Open the target Databook.

  2. Open permissions

    Click File Action menu (...) > Manage Permissions.

  3. Find users/groups

    Search for users or groups.

  4. Assign level

    Assign Viewer, Editor, or Owner.

  5. Save

    Save changes.

Row-Level Security

  1. Add access column

    Create a column identifying access boundary (for example, Region or Department).

  2. Map access rules

    Map user groups to allowed values.

  3. Validate visibility

    Users see only rows matching their assigned values.

Best Practice: Assign permissions to groups rather than individuals. Every Databook should have at least two Owners.

hub How to Connect Across Databooks

Databooks can reference each other through cross-Databook lookups.

How It Works

  1. Create lookup column

    In Databook A, create a lookup column.

  2. Set external source

    Set the constraint to reference a table in Databook B.

  3. Select linked values

    Users in Databook A select values from Databook B.

Use Cases

Scenario Setup
GL accounts linked to cost centres Cost centres in Databook A; GL mappings in Databook B with lookup to A
Employees linked to departments Departments in one Databook; employees in another with lookup
Products linked to categories Category hierarchy in one Databook; products in another with lookup

When source data updates, relationships remain intact.

history How to Track Changes

Version History

Every change is logged automatically:

  • Who made the change
  • When it was made
  • What values existed before and after

Viewing History

  1. Open history

    Open Databook or table, then click History (or File Action Menu > View History).

  2. Filter

    Filter by date, user, or change type.

  3. Restore

    Select a previous version and click Restore if needed.

Lineage

See where data comes from and where it is used:

  • Upstream: Imports or source systems feeding this Databook
  • Downstream: Reportbooks that consume this Databook
Tip: Check downstream lineage before structural changes to understand report impact.

verified Why It Matters

Benefit How Databooks Deliver It
Data quality Typed columns and validation prevent bad data at entry
Single source One place for reference data; Reportbooks pull live
Audit trail Every change tracked with user and timestamp
Access control Permissions at databook, table, or row level
Relationship integrity Lookups maintain links; broken references flagged
Hierarchy support Parent-child structures with tree view
Last updated
March 2026
Audience
All Clarity users
v2.0 | 20260312