Dashboard

Import / Export

This is how you get data into a project and back out again. You can bring in a spreadsheet, see exactly what was loaded, and download any table as a file whenever you need it.

Before you start, check these three things:

1. Pick the right project. Use the project switcher at the top of the screen. Everything you import goes into the project shown there.
2. Have your file ready. Imports use CSV files (a spreadsheet saved as "comma-separated values"). In Excel or Google Sheets, choose File → Save As / Download → CSV.
3. Make sure the first row is headings. The top row of your file should name each column (for example Tag, Description, Location). The app uses those names to label the data.

Import a spreadsheet

Importing happens in four numbered steps, shown along the top of the page. You move through them with the Next and Back buttons, so you can always go back and change something.

Step 1 — Select Source. Open Import/Export → Import Data. Under CSV / Spreadsheet, choose:

• Select File — pick a single CSV file from your computer.
• Select Folder — pick a whole folder; the app finds every CSV inside it so you can import several in one go.

Step 2 — Setup Import. Tell the app where the data should go by choosing an Import Mode (explained in the next section), then check how your file's columns line up with the table. The app matches columns with the same name automatically — you only step in where a column is unmatched or its type looks wrong.

• File Column Name is what your spreadsheet calls it.
• Table Column Name is where it will be stored.
• Sample Values shows a few real values so you can confirm it's the right column.
• Assigned Type is the kind of data (text, number, date, yes/no). Change it only if the app guessed wrong.

Step 3 — Optional Settings. Add any optional details, such as the categories a new table belongs to. You can leave these as they are and move on.

Step 4 — Import. Select Validate & Import. The app first checks every row, then loads the good data. When it finishes you'll see a confirmation and a count of the rows imported.

Choosing an import mode

The import mode tells the app what to do with your file. There are three choices — here's when to use each.

Checking your import

Before anything is saved, the app validates your file and shows a report. This is your chance to fix problems.

• If every row is valid, the import runs and you see how many rows were added.
• If some rows have problems, the report lists each one — the row number, the value, and what's wrong (for example a word where a number was expected).

Select Download Error Report (CSV) to get the list as a file. Open it in your spreadsheet, fix the flagged rows in your original file, and import again.

The Import Log

The Import Log is a history of every import for this project — what was loaded, when, and whether it succeeded. Open it from Import/Export → Import Log.

Each row shows the file name, the table it went into, how many rows and columns were loaded, the status, and the date. Use the From and To date boxes to narrow the list, then select Apply; Clear resets it.

Exporting data

Exporting downloads a table as a CSV file you can open in Excel or share with others. Open Import/Export → Export Data.

1. Choose what to export: Export System Table (a built-in table) or Export Custom Table (one you imported).
2. Pick the specific table from the list that appears.
3. Select Export. Your browser downloads the file.

Two optional settings let you include extra detail:

• Include system columns — adds the app's housekeeping columns (who created or changed each row, and when). Leave this off for a cleaner file.
• Include deleted records — adds rows that were deleted but not permanently removed. Leave this off to export only current data.

Field reference

Every setting on the Import and Export screens, in plain words.

Tips & common mistakes

• Wrong project selected. If your imported data doesn't appear, check the project switcher at the top — the data may have gone into a different project.
• File isn't a CSV. A normal Excel file (.xlsx) won't work. Save it as CSV first.
• Missing headings. If the first row holds data instead of column names, the app treats your real first row as headings. Add a heading row and re-import.
• Numbers that contain text. A column meant to be numbers will fail if some cells contain words or symbols. Clean those cells, or change the column's type to text.
• Re-importing duplicates data. To refresh an existing custom table rather than add a second copy, use Import Into Custom Table, not Create New Custom Table.

Data Quality

Data Quality lets you write checks — simple rules that find rows with problems. A check might be “every asset must have a description” or “the cost can’t be negative”. The app runs your check across the table and shows you exactly which rows fail, so you can fix them.

A check is made of one or more conditions. Each condition names a column, a rule type (what to test for), and sometimes a value. A row passes when it satisfies the rule and fails when it doesn’t — and failing rows are what you’re looking for.

Before you start, check these three things:

1. Pick the right project. Use the project switcher at the top. Checks belong to the project shown there.
2. Have some data to check. You need at least one table with rows in it — import a spreadsheet first if you haven’t (see the Import section above).
3. Know what “good” looks like. Decide the rule in plain words first — “the tag can’t be blank”, “status must be one of three words” — then build it.

Create a check

Open Data Quality and select + New Check. A window opens with three numbered steps along the top — Rule, Scope, and Preview. Move through them with Next and Back; nothing is saved until the final step.

Step 1 — Rule. This is where you describe the problem to look for.

1. Pick a table from the Table list. The columns in that table become available to test.
2. Under Rule Logic, select + Add condition. A condition row appears with three parts: Column, Rule Type, and (for most rule types) a Value.
3. Choose the Column to test, then the Rule Type (see The check types below), then fill in the value if one is needed.

You can leave the Rule Name blank — the app names the check from its conditions automatically. Type your own name if you’d prefer something memorable.

Step 2 — Scope (optional). By default a check runs over the whole table. Scope lets you narrow it to some rows — for example only active assets. Most checks don’t need this; see Scope below.

Step 3 — Preview. The app runs your check and shows the rows that fail, so you can confirm it’s finding the right thing before you save. When you’re happy, select Save Check.

The check types

When you choose a Rule Type, the choices are grouped by what they do. The list adapts to the column: a number column offers ranges, a text column offers length and pattern checks. Here is every type, in plain words, with an example.

Completeness — is there a value at all?

Range — is a number or date within bounds?

Comparison — does it match an exact value?

Membership — is it one of an allowed set?

Length — how many characters?

Text matching — does the text contain something?

Patterns — does it follow a format?

Uniqueness — is the value repeated?

Conditional completeness — required only sometimes.

Combining conditions

A check can have several conditions. Select + Add condition again to add another; each new one is joined to the previous with AND or OR, which you can switch.

• AND — a row must satisfy both conditions to pass. Use it to combine requirements: “Tag is not empty AND Status is in the allowed list”.
• OR — a row passes if it satisfies either condition.
• Clone — the copy button on a condition duplicates it, handy when the next one is nearly the same.
• Remove — the remove button deletes a condition (available once you have more than one).

Scope: checking only some rows

Step 2, Scope, limits which rows the check runs against. Leave it empty to check the whole table; add a filter to check only the rows that matter.

It works just like Step 1: select + Add scope filter, then pick a column, a rule type and a value. Only rows that match the scope are tested — the rest are ignored entirely (they can’t pass or fail).

Example. To check that only in-service pumps have a last-inspected date, set the scope to Status equals “In Service”, and the rule to Last Inspected is not empty. Retired pumps are skipped.

Cross-table checks

Some rules span two tables that are linked by a relationship — for example Equipment and its Maintenance Records. A cross-table check lets you say things like “every pump must have at least one maintenance record”.

If the table you picked is linked to another, a + Add cross-table condition button appears next to + Add condition. (No relationships, no button — single-table checks are unaffected.) Relationships are set up under Settings → Relationships.

A cross-table condition has three parts:

1. Related table — which linked table to look in (for example Maintenance Records for each Pump).
2. On related column (optional) — a test on a column of the related rows, such as Status equals “Closed”. Leave it as “any related row” to simply check that related rows exist.
3. Requirement — how the related rows must behave:
   • At least one related row matches (or exists).
   • Every related row matches.
   • No related row matches (or exists).

Compare two related columns. When you test a related column, you can compare it against a value or against another column on the same related table — for example every maintenance record where End Date is on or after Start Date.

Filtering related rows

Sometimes a cross-table rule should apply to only some of the related rows — “every Closed maintenance record has a completion date”, not every record. The Only related rows where… filter does exactly that.

Under a cross-table condition, add one or more filter clauses. Each names a related column, a rule type and a value (or another column). Only related rows that match the filter are considered; the rest are ignored.

• Add several clauses joined by AND or OR — for example “Status equals Closed AND Priority equals High”.
• Compare to another column — a clause can compare two related columns, e.g. “Actual Cost is greater than Budget”.

Worked example. To enforce “every Closed maintenance record has a completion date”: related table Maintenance Records, tested column Completion Date is not empty, requirement Every related row matches, and the filter Only related rows where Status equals “Closed”. Pumps whose open records lack a date are not flagged — only closed ones must have it.

Preview & results

Step 3 shows how your check performs against real data before you save it, and the same results appear whenever you open a saved check.

• Failing / Passing toggle — switch between the rows that fail the check (the default, the ones to fix) and the rows that pass.
• Counts — you see how many rows were checked and how many failed.
• Paging — use Prev and Next to move through the failing rows a page at a time.

Managing checks

The main Data Quality screen lists every check in the project, with its pass/fail figures at a glance.

• Group by — arrange the list by Table Name, Table Category, or see All Checks together.
• Edit — reopen a check in the builder to change it.
• Activate / Deactivate — turn a check off without deleting it; deactivated checks stop running but are kept.
• Delete — remove a check for good.

Field reference

Every setting on the check builder, in plain words.

Tips & common mistakes

• Everything fails. Usually the rule is too strict or points at the wrong column. Open Preview and check a couple of the “failing” rows — they often reveal the mistake.
• Nothing fails, but you expected problems. Check the column and the value — a stray space or different spelling (“In service” vs “In Service”) can make a rule match nothing. Case is ignored unless Match case is ticked.
• Blank cells and completeness. Most rules treat a blank cell as passing (there’s nothing to test). To require a value, add a Not empty condition as well.
• In list needs commas. For In list, separate the allowed values with commas: In Service, Standby, Out of Service.
• Cross-table button missing. The + Add cross-table condition button only appears when the table is linked to another under Settings → Relationships.
• Wrong project. Checks belong to the project in the switcher at the top — if a check isn’t where you expect, confirm the project.

FMECA

FMECA stands for Failure Mode, Effects & Criticality Analysis. It is a structured way to ask, for a piece of equipment, “what can go wrong, what happens when it does, and how much does it matter?” The answers help you decide where to focus inspection, spares and maintenance effort. This module follows two industry standards — ISO 14224 (the standard vocabulary of equipment and failure modes) and NORSOK Z-008 (the method for rating criticality) — so your analysis speaks the same language as the rest of the industry.

You reach it from Build → FMECA. The screen has three tabs, and you work through them roughly left to right:

• Function hierarchy — describe what the equipment is meant to do (its functions) and how serious it is if each function is lost.
• Worksheet — the FMECA itself: one row per failure mode, with its effects, cause and criticality.
• Standard library — the ISO 14224 catalogue of failure modes, mechanisms and detection methods you pick from as you fill in the worksheet.

Before you start, check these three things:

1. Pick the right project. Use the project switcher at the top. Everything you build here belongs to the project shown there.
2. Have your equipment (tags) in the project. An FMECA is done against a real asset — a tag. Import or add your equipment first (see the Import section above) so the pump, valve or vessel you want to analyse is available to pick.
3. Know the equipment’s job. Have a one-line description of what the item does and what depends on it — you’ll turn that into its functions in the first tab.

Seed the standards

The very first time you use FMECA in a project, load the standard reference data. This fills the library with the ISO 14224 failure modes, mechanisms and detection methods, and adds the Z-008 template sub-functions you’ll build on. You only do this once per project.

Select Seed ISO 14224 + Z-008 standards at the top of the screen. After a moment you’ll see a confirmation, the Standard library tab fills with entries, and a Standard sub-function library appears at the bottom of the Function hierarchy tab.

Build the function hierarchy

Z-008 rates criticality by function, not by the box of metal — so you start by describing what the equipment does. A Main Function (MF) is the top-level job; each MF is broken into Sub Functions (SF), the individual duties that deliver it. You then rate how serious losing each one would be.

Step 1 — Add a Main Function. On the Function hierarchy tab, select Add Main Function and fill in the form:

• Code and Name — a short reference and an active-verb description of the job (“Transfer feed to the reactor”).
• System — the process system or area it belongs to (optional).
• Redundancy — is there a spare? A = none (single unit), B = one parallel/standby unit, C = two or more.
• Consequence — Safety / Environment / Production / Other — how bad is it if this function is lost, in each category? Use your project’s consequence classes (for example C1 low … C3 high).

Step 2 — Add its Sub Functions. On the new main-function card, select + Sub function for each duty and rate it the same way. Give the main duty its own row, plus any support duties such as local indication or condition monitoring.

You don’t have to invent sub-functions from scratch: Seed standard sub-functions adds the Z-008 Table B.1 templates (pressure relief, shutdown, monitoring, local indication, and so on) as a starting library you can copy and adapt.

Each row carries classification badges — a RED badge for redundancy and an S/E/P/O badge summarising the four consequence classes — so the whole hierarchy can be read at a glance.

Assign your tags (equipment)

A function is a template; a tag is the real piece of equipment that delivers it. Linking your tags to sub-functions records which assets each function applies to, and lets you flag the one the function matters most for.

On a sub-function row, select + Tag, choose the equipment tag, and tick Most critical SF for this tag if this is the function that makes this asset critical. Assigned tags appear as chips on the row; the most-critical one is marked with a star (★).

Create an analysis

An analysis is one FMECA study — usually one tag against one sub-function. It’s the container the worksheet rows live in. Move to the Worksheet tab and select New analysis.

• Code and Name — a reference and a readable title.
• Tag (asset) — the equipment being analysed.
• Sub function — the function this study covers.
• Method — how you’ll rate criticality: Z-008 consequence, RPN (S×O×D), or Both. See Criticality below.

Once saved, the analysis is selected in the Analysis dropdown and a summary line shows its status, method, tag and sub-function. You’re ready to add worksheet lines.

Fill in the worksheet

The worksheet is the heart of the FMECA. Each line is one way the function can fail. With your analysis selected, choose Add line and describe the failure:

1. Failure mode — how it fails, chosen from the ISO 14224 list (for example FTS — Fail to start on demand).
2. Mechanism — the underlying physical process (wear, corrosion, fatigue…), also from the standard list.
3. Detection method — how the failure would be found (functional test, condition monitoring, inspection…).
4. Effects — Local / System / End — what happens right at the item, to the wider system, and to the end result. (“Pump won’t start” → “no feed flow” → “reactor feed interrupted”.)
5. Cause — the root cause, in your own words.
6. Severity (S) / Occurrence (O) / Detection (D) — each rated 1–10 for the RPN (see below).
7. Consequence class — the Z-008 class for this failure (for example C3).

Add a line for each credible failure mode. The completed worksheet shows every failure side by side, with the RPN worked out for you and the consequence class alongside — the full picture of how the pump can fail and which failures matter most.

Criticality: Z-008 and RPN

The module gives you two ways to score how much a failure matters. They answer slightly different questions, and you can use either or both — that’s the Method you picked on the analysis.

RPN — Risk Priority Number. A classic FMEA score, worked out per worksheet line as:

RPN is quick and familiar, and it rewards detectability: a failure that’s hard to spot rises up the list even if each single event isn’t catastrophic. In the worked example, the slow low-output impeller wear tends to score the highest RPN because it’s hard to detect.

Z-008 consequence class. A function-level view: how serious is the loss across Safety, Environment, Production and Other, taking redundancy into account. The worst of the four categories dominates — a failure that’s C3 for Production is a C3 failure. This is the view that flags fail to start (a complete loss of the pumping function) as top criticality, regardless of how easy it is to detect.

The standard library

The Standard library tab is the reference catalogue you pick from when filling in worksheet lines. It’s read-only browsing — you don’t normally edit it — but it’s useful for seeing the exact ISO 14224 codes and their meanings.

Field reference

Every field across the FMECA forms, in plain words.

Tips & common mistakes

• Nothing to pick in the worksheet. If the failure-mode or mechanism lists are empty, you haven’t seeded the standards yet — select Seed ISO 14224 + Z-008 standards first.
• No tag to choose. The equipment must exist in the project before you can assign it or analyse it. Import or add the asset first.
• Add a main function before a sub function. Sub functions hang off a main function, so create the MF first — the sub-function form needs one to attach to.
• Describe the function as a job, not the object. “Transfer feed to the reactor” (a verb) works better than “Pump” (a noun) — criticality is about the job being lost.
• Worst category wins. Under Z-008 the overall class is the worst of Safety / Environment / Production / Other — don’t average them.
• Detection is “hard to catch”, not “easy”. For RPN, a high Detection number means the failure is hard to detect (worse). A failure caught early by monitoring scores low.
• Wrong project selected. Functions, analyses and worksheets belong to the project in the switcher at the top — if something’s missing, confirm the project.

Data Viewer

The Data Viewer is where you look at, search and edit the data in a project. Every table you import or build shows up here as a familiar grid of rows and columns — and from this one screen you can filter it, group it, fix problems, track progress and export it again.

It’s the busiest screen in the app, so it helps to know the shape of it before diving in. There are four areas, top to bottom:

• The toolbar (across the top) — which table you’re looking at, and the tools for shaping the view: Layouts, Columns, Filters, Group, Transform and Options.
• The grid (the middle) — your rows and columns. You edit a value by clicking straight into its cell.
• The selection bar (just below the grid) — appears when you tick rows, with actions such as Add Row, Clone, Delete, Lock and Export.
• The pager (the bottom) — moves through the pages of rows and sets how many you see at once.

Before you start, check these two things:

1. Pick the right project. Use the project switcher at the top of the screen. The Data Viewer only ever shows the data in the project shown there.
2. Have some data. The viewer shows tables you’ve imported or created. If a project is brand new, import a spreadsheet first (see Import a spreadsheet above) — until then the viewer shows a “No Data Exists” message with an Import Data link.

Finding & opening a table

A project can hold dozens of tables, so the Data Viewer opens with a table picker — a browse-and-search panel for choosing which one to work on. Once you’re in a table, a single button brings the picker back so you can switch.

Step 1 — Open the Data Viewer. Choose Data Viewer from the main menu. If the project has data, the table picker opens automatically; if it doesn’t, you’ll see “No Data Exists” with an Import Data link instead.

Step 2 — Find your table. The picker has two parts:

• The category list (down the left) — tables are grouped by their category (the labels you gave them on import, or “Uncategorized”). Select a category to narrow the list.
• The table list (the main area) — every table in the chosen category, each shown by name so you can recognise it at a glance.

To jump straight to a table by name, type into the Search tables… box at the top — the list filters as you type.

Step 3 — Open it. Select a table and it loads into the grid. The picker closes and the table’s name appears at the top next to Table:.

Switching tables later. The current table’s name sits at the top-left of the toolbar. Select the list button (the three-lines icon) next to it to reopen the picker and choose a different table at any time.

Reading the grid & Options

Your data fills the middle of the screen as a table of rows and columns. A few controls change how it looks and how much summary it shows — none of them change the data itself.

Moving through the rows. The bar at the bottom is the pager. Per page sets how many rows you see at once (10, 25, 50, 100, 250 or 500 — 25 to start). The arrows move to the first, previous, next and last page, and the message on the left reads Showing 1–25 of 340 so you always know where you are.

The Options menu. Select Options in the toolbar for a short menu of view settings:

• Show gridlines — the cell border lines. Turn them off for a cleaner look.
• Show column types — a small icon next to each heading showing the kind of data (text, number, calendar, and so on).
• Progress Stats — how the progress summary is drawn: Off, Cards (one tinted card per status), or Bar chart (a single stacked bar).
• Status Bar — Visible — shows or hides the bottom bar that holds the row-action buttons and the selection totals.

The progress summary. If a table tracks a workflow status, the summary shows how the rows in view are split across those statuses — each with its percentage and count. It reflects whatever you’ve filtered to, and updates the moment you change a row’s status. Tables without a status column simply don’t show it.

Selection totals. Tick some rows, or drag to select a block of cells, and the right of the bottom bar shows live totals: Rows and Count (of cells) always, plus Sum, Average, Min and Max when every selected cell is the same kind of value (all numbers, or all dates). Mixed or text selections show a dash for those.

Choosing which columns to show

Wide tables are easier to read when you hide the columns you don’t need right now. The Columns button does that — and lets you reorder columns and jump to one.

The button shows a visible / total count, for example Columns 7/9. Select it to open the panel:

1. Tick or untick a column to show or hide it. All shows every column; None hides them all (except the row-label column, which always stays).
2. Search columns… filters a long list by name.
3. Drag the handle (::) to reorder columns. (Reordering is paused while a search is active.)
4. Select a column name to scroll the grid sideways straight to it.
5. Select Apply to commit your changes, or Cancel to discard them.

Tree & Flat view

When a table’s rows have parents and children — an area that contains equipment, a pump made up of parts — you can view it as a tree instead of a flat list, and expand each branch to see what’s under it.

A Tree / Flat toggle appears next to the table name, but only for tables that have a parent link. Tables with no parent-child relationship are always flat, and the toggle simply isn’t shown.

• Flat (the default) — the ordinary paged list. It also offers two extra sortable columns, Level and Path, so you can still see where a row sits in the hierarchy.
• Tree — rows nested under their parents. Select the chevron on a row to expand it and load its children; the headings stay pinned at the top and the label column stays anchored on the left as you scroll.

Finding a row in a big tree. In tree view the Filters button is replaced by a Find… box (filtering a tree would hide rows whose parents were filtered out, which makes no sense). Type two or more letters and it lists matching rows, each with a breadcrumb trail of its ancestors. Pick one and the tree expands to it, highlights it and scrolls it into view — the tree itself stays whole.

Filters & row status

The Filters panel is how you narrow the grid to just the rows you care about. It gathers everything in one place: which kind of rows to show (their status), and then any number of conditions across four tabs.

Select Filters to open the panel. Two small chips on the button tell you the current state at a glance: the scope (Active, Locked…) and a count of how many conditions are applied.

Row status. At the top, the Status control chooses which rows are in scope — pick one:

The four tabs. Beneath Status are the condition tabs, each covered in its own section next: Column Filters, Quality, Linked Data and Work. (Linked Data and Work only appear when they apply.)

Applying. Nothing you change here affects the grid until you select Apply. Clear Filters clears just the tab you’re on; Clear All wipes every tab; Cancel closes without applying.

Column filters

The Column Filters tab keeps only the rows whose values match conditions you set — “Area is 100”, “Cost is more than 500”, “Description contains pump”.

1. Select + Add Filter. A row appears with a column picker.
2. Choose a column. The available operators and the value box adjust to that column’s type.
3. Pick an operator and enter the value, then Apply.

The operators depend on the kind of column — text offers Contains, Starts With, In List…; numbers and dates offer Greater Than, Between, Before/After…; yes/no columns offer True/False; a status column offers Is / Is Not with a list of your statuses. For Between you get two boxes joined by “and”; for In List a Paste values button lets you paste a whole list at once.

Quality filters

The Quality tab connects the viewer to your Data Quality checks, so you can pull up exactly the rows that fail a check and fix them in place.

1. Open Filters → Quality. The tab lists this table’s checks, each showing its failure count — for example “12 Failures (4%)” or “Passing”.
2. Use Failing / All to show only checks that currently fail (the default) or every check, and the Search checks… box to find one by name.
3. Tick one or more checks — they appear as chips at the top — and select Apply. The grid switches to the failing rows, with the problem cells highlighted.

Where a check can be fixed automatically, a Fix failures button appears on it — see Fixing data-quality failures.

Linked Data filters

When a table is linked to others — equipment to its work orders, assets to their documents — the Linked Data tab filters rows by whether they have or don’t have related records.

This tab appears only when the table has linked tables. To use it:

1. Select + Add Condition.
2. Choose a linked table, then Has records or No records.
3. Add more conditions if you need them, joined by AND or OR, then Apply.

Work filters

If your project divides records into work areas (“segments”) with people assigned to them, the Work tab narrows the grid to the records that belong to someone’s assignment.

This tab appears only if you hold a role on the table. Tick Show only records assigned by segment, then set:

• Whose work — Me, a named teammate, Anyone (any assigned segment), or Unassigned (records whose segment has nobody working it — a good way to find gaps).
• Segment — narrow to one segment, or leave it on all.
• Status category — tap the pills (Not started, In progress, Awaiting approval, Approved…) to include only certain workflow stages.

Grouping rows

Grouping collapses the grid into buckets by one or more columns, each showing how many rows it holds — a quick way to see “how many assets per area” or “how many jobs per status”.

1. Select Group.
2. Pick a column from + Add column… — it becomes a chip. Add more to nest the buckets (the order matters).
3. Select Apply. Each bucket shows its value and a count; select one to expand it and load its rows.
4. Select Clear to return to the normal list.

Editing cells

You edit data straight in the grid. Double-click a cell to open an editor suited to that column, change the value, and it saves.

• Commit with Enter or by clicking away. Cancel with Esc. A long-text cell opens a small box with its own Save and Cancel.
• The editor matches the column: a text box, a number box, a yes/no dropdown, a date picker, or a search box for columns that link to another table (you pick a record, you don’t type it).
• The cell flashes when saved. If the value doesn’t fit the column, a message explains and the old value stays.

Filling many cells at once. Select a block of cells in a single column and paste or fill a value to set them all together. Cells where the value doesn’t fit the column’s type are left unchanged and reported.

Adding & cloning rows

New rows are added straight into the grid, and existing rows can be copied one at a time or in bulk. These buttons live on the bottom bar.

Add Row. Select Add Row and a blank draft row appears at the top with a New badge. Fill its cells (the row’s key is required first), then Save Row — or Cancel to discard it.

Clone Row / Clone ×N. Select one row, then:

• Clone Row makes a single copy as a draft (with the key left blank for you to set) that you can tweak before saving.
• Clone ×N makes many copies at once — choose how many (up to 500); each gets a new key generated from the original, and any key that already exists is skipped.

Clone Tree. In Tree view, selecting a node offers Clone Tree — it copies that node and everything under it as a new branch, rewriting the keys with find/replace rules you set. Every new key must be unique or the whole clone is blocked (a tree can’t skip a node without orphaning its children).

Deleting, locking & the recycle bin

Deleting a row moves it to a recycle bin rather than destroying it, and locking a row freezes it so nobody edits it by accident. Both act on the rows you’ve ticked, using the buttons on the bottom bar.

Delete and restore. Select rows and choose Delete; they move to the recycle bin (a “soft delete” — reversible). To bring them back, open Filters → Status and choose Deleted: the grid now shows deleted rows and the button becomes Restore.

Lock and unlock. Select rows and choose Lock to freeze them — locked rows are highlighted and their cells can’t be edited. The same button reads Unlock when the selected rows are locked; on a mixed selection it lets you choose which to do.

Transform preview & rulesets

The Transform panel cleans up text columns — trimming spaces, changing case, find-and-replace, expanding abbreviations — and lets you preview the result before deciding whether to save it. Its subtitle says it plainly: “Preview only. No database changes.”

Previewing a clean-up.

1. Select Transform, then + New Set.
2. Tick the text columns to work on under Columns (Text/Varchar).
3. Add one or more Steps (trim, upper/lower case, find & replace, and so on); they run top to bottom.
4. Select Apply Preview — the grid shows the cleaned values in extra preview columns alongside the originals. Nothing is saved. Clear turns the preview off.

Saving and applying for real. When a set targets a single column and you’re happy with it, Save as ruleset stores it in the library (either Shared with project or Private to me) so it can be reused. To write the change to the data, Apply a ruleset: a dialog reports how many rows it will change (“…X rows to change · Y unchanged · Z locked, skipped”), then Apply to database writes it — to every row matching the current filters, recorded in the history, skipping locked rows.

Fixing data-quality failures

Some quality checks come with a built-in fix. For those, the Quality tab shows a Fix failures button that repairs the failing rows automatically.

1. Open Filters → Quality and find a failing check with a Fix failures button.
2. Select it. The Fix failing rows dialog previews the effect — “N failing rows · X will be fixed · Y already valid · Z locked, skipped”.
3. Select Fix failing rows. It applies the check’s fix, re-checks, and reports how many now pass.

Progress, status & approvals

Many tables track each row through a workflow — not started, in progress, awaiting approval, approved. The Data Viewer shows that progress, and lets the right people move records along and approve them.

Seeing progress. The progress summary at the top shows how the rows in view split across the statuses, as cards or a bar. Each row also has a small clock that opens its Progress Timeline — a read-only history of who moved it, when, and any comments.

Moving records along. Tick one or more rows and a Status actions panel appears on the right, listing the moves you’re allowed to make — Submit for approval, Approve, Reject…, Mark complete, and so on. Select one; if the status needs a comment you’ll be asked for it.

Who can do what. Records are grouped into segments (by one column’s value, such as discipline). Each segment has builders who submit work and approvers who pass or reject it — so you only ever see the actions your role allows for that record. For safety you can’t approve a record you edited yourself; someone else has to.

Change history

Every edit is recorded, so you can always see what a value used to be and who changed it. Right-click any cell for two history views.

• Cell Change History — the story of that one cell: its current value, then each previous value with who changed it and when. Any earlier value has a Revert button to put it back.
• Column Change History — every change to that column across all rows, newest first, with the row each change belongs to. This one is read-only and paged.

Layouts

Once you’ve arranged a table just how you like it — the right columns, order, filters, grouping and status — a Layout saves that whole arrangement under a name so you (and your team) can recall it in one click.

The Layouts button shows the current layout’s name, or Unsaved when you’ve changed things. In the panel:

• Layout — choose a saved layout and select Apply.
• Save — update the current layout with how the table looks now.
• More — Save As (a new named layout), Rename, Set Default (the one a table opens with), or Delete.

A layout remembers your column choice and order, filters, sorts, grouping, quality selection, row status, Tree/Flat mode and the display toggles. It doesn’t store a transform preview.

Table settings & lifecycle

The Actions menu holds a table’s own settings and the actions that create, empty or remove it.

Table Settings opens a two-tab window:

• General — the Row Description (the human-readable name shown for each row across the app), a Use as a reference / base table tick for lookup tables (equipment types, locations…) so they’re offered first as link targets, and the table’s Categories.
• Structure — the Unique Row Identifier that uniquely identifies each row (used to link tables together), and a Parent table + Parent label column to build a hierarchy for Tree view.

Clone / Clear / Delete. Clone Table makes a copy (optionally with its data and its quality checks). Clear Table empties every row but keeps the table. Delete Table removes the table and all its data for good.

Exporting

Two buttons on the bottom bar download what you’re looking at as a CSV file you can open in Excel.

• Export Page to CSV — just the rows on the current page.
• Export All to CSV — every row matching your current filters.

Field reference

The main buttons and controls of the Data Viewer, in plain words.

Tips & common mistakes

• “I filtered but nothing changed.” The Filters panel only takes effect when you select Apply. Closing it another way leaves the grid as it was.
• “A column is missing.” It may be hidden — open Columns and tick it. Hidden columns also can’t be filtered until they’re shown.
• “A cell won’t let me edit it.” Check whether the row is locked, you’re in the Deleted view, or the table is a read-only built-in / integration table. Housekeeping columns are never editable.
• “My rows disappeared after I deleted them.” They’re in the recycle bin. Set Filters → Status to Deleted and select Restore.
• Preview isn’t the same as saving. A transform preview changes nothing — only Apply to database does, and it affects every filtered row, not just the page.
• Layouts are shared. Renaming or deleting one changes it for everyone on the table — name them clearly and delete with care.
• “I can’t approve my own record.” That’s deliberate — whoever edits a record can’t also approve it; another approver must.
• Clearing or deleting a table is permanent. Only deleting rows is reversible (via the recycle bin).
• Wrong project? The viewer only ever shows the project in the switcher at the top — if a table is missing, check you’re in the right project.