On this page
- How to: create and use a dataset
- Define the columns
- Maintain rows
- Import rows from CSV or Excel
- Export rows as CSV
- Sync with an Excel file
- Fill a field from a dataset
- Entry missing? Add or suggest it
- Protect and update values
- Make the choice depend on another field
- Set target and deadline for the stacked view
- Add billing details
How to: create and use a dataset
- 1In the menu, open Templates and the Datasets tab.
- 2Click **+ at the top left, enter a name such as “Suppliers” and click Create**.
- 3Add the columns under Columns. The first becomes the key column that is searched.
- 4Click Add row and enter the values. Or load them via Import file.
- 5In a template, give a field the type From dataset and pick your dataset there.

- 1**+** creates a dataset
- 2Connect to Excel
- 3Import file
- 4Columns: the schema of every row
- 5Add row
A dataset belongs to the organization, not to one template. Maintain it once and it is up to date in every template. Datasets and columns need the Manage templates right; for rows, Maintain datasets is enough.
Duplicate, rename or describe a dataset
- Duplicate dataset in the ⋮ menu at the top right creates “<name> (Copy)”, with all columns and rows, archived ones too.
- An Excel connection, the history and open suggestions are not copied.
- To change the name, use the pencil icon next to it.
- The description sits below the name and also in the list on the left. If there is none, click Add description.
Define the columns
The columns are the schema for every row. Each column has a label, a type and a technical name that is created for you. Once the dataset has rows, the Columns card is collapsed; click its header to open it.

- 1Type of the column
- 2Key: exactly one column
- 3Required
- 4Add column
- 5Billing details
| Type | What for | Good to know |
|---|---|---|
| Text | Names, places, identifiers | Usual for the key column |
| Number | Quantities, prices, targets | Can carry a unit, such as €, pcs or h |
| Date | Deadlines, appointments | Enter as DD.MM.YYYY |
| Contact addresses | — | |
| Yes/no | Flags such as “active” | — |
| Formatted text | Service descriptions with paragraphs, lists and tables | Never the key, not in the match list, not translated |
| Reference → <dataset> | Entries of another dataset, such as a contact’s company | Never the key |
| Setting | What it does |
|---|---|
| Key | This column is searched and its value names the entry. Duplicate values block the switch. |
| Required | Empty cells in this column count as incomplete. |
| Unit | Number columns only. It shows in the rows table and with the target in a stack’s “Whole inventory” box. |
| Handle ⋮⋮ | Drag to reorder the columns. |
| Trash icon | Removes the column. While the notice shows at the bottom, Undo brings it back with its values. |
| Language picker top right | With a target language you enter translated column names. Translate › jumps to the missing ones. |
If you switch a column with values to number, date, email, yes/no or reference, Bricksta checks every value first. If one doesn’t fit, such as “ca. 90k” in a number column, the type stays. The message lists the values and the cells are marked red.
Reference columns in detail
- Bricksta remembers the entry, not just its name. Rename it in the target and the name follows in every row.
- Merge two entries in the target and the references point to the one that stays.
- A referenced entry can only be archived, not deleted. A dataset that a column points to stays as well.
- Nobody can newly assign an archived entry, not via import either. Existing assignments stay.
Formatted text in detail
- Paragraphs, bold, bullet lists, numbered lists and tables with a header row and merged cells are allowed.
- The rows table shows only the beginning; a click opens the editor. Nothing is saved until you click Save.
- Insert table adds a table. The Table menu inserts rows and columns, merges or splits cells.
- Drag the line between two columns to set their widths. The display and the quote PDF use the same split.
- Limits: 20,000 characters, 8 columns and 500 rows per table. The counter below the editor shows where you stand.
Maintain rows
Click Add row and type into the cells. Bricksta saves a value when you leave its cell. If someone maintains the same dataset at the same time, you see their changes without reloading.

The end of each row shows how many cases use the entry, such as “3 cases”. Next to it, ⋯ opens the row menu. Drag the handle ⋮⋮ to reorder rows.
| In the row menu | What happens |
|---|---|
| Duplicate … | A copy appears right below, its name gets “(Copy)”. Its history starts fresh. |
| History of … | Who created, changed (old → new), archived or merged the row and when, including by import or from Excel. |
| Archive … | The entry can no longer be picked, existing cases keep it. Show archived and Reactivate … bring it back. |
| Merge … into … | For duplicates like “MSD GmbH” and “MSD”: running cases show the one that stays, the other is archived. |
| Delete … | Cases with this entry lose their reference, the notice gives their number. Undo brings the row back. |
If an entry should stay in old cases, archive it instead of deleting it. Completed cases and those awaiting approval keep the old name when you merge.
Import rows from CSV or Excel
- 1Select the dataset and click Import file at the top right.
- 2Choose a CSV or Excel file (.xlsx). Its first line holds the column names.
- 3If the file has several worksheets, you pick one. Bricksta creates missing columns.
- 4Check the preview: new, changed, unchanged and skipped, each with the reason.
- 5Click Apply rows. If one row fails, the whole dataset stays unchanged.

- 1Import file
| If … | then … |
|---|---|
| the key already exists in the dataset | the entry is updated, not duplicated. |
| a cell in the file is empty | the existing value stays. |
| a CSV value contains a comma or line break | put it in quotes, such as "München, DE". |
| the file is in the old .xls format | save it as .xlsx in Excel. |
| dates or numbers come from Excel | they fit date and number columns without reformatting. |
| the target is a “Formatted text” column | the value arrives as plain text, a blank line separates paragraphs. |
| the dataset is connected to Excel | the new rows go into the file with the next sync. |
Export rows as CSV
Click Export CSV next to Import file. The file holds every non-archived entry and opens straight in Excel. Import it unchanged and the preview reports 0 changes.
If a value starts with =, +, - or @, an apostrophe goes in front of it. That stops Excel from running it as a formula. Bricksta strips the apostrophe when reading the file back.
Sync with an Excel file
If a list already lives in Excel on OneDrive or SharePoint, Bricksta syncs it hourly in both directions. The file needs a formatted table for this (“Format as Table” in Excel).
- 1Click Connect to Excel and, if needed, connect your Microsoft account with file access.
- 2Pick the file under Recent, My files or Shared with me, or search for its name.
- 3Pick the table and map the columns. The key column must be included.
- 4The last sync now shows above the rows table. Sync now starts it right away.

- 1Connect to Excel
| Case | What happens |
|---|---|
| The same cell was changed on both sides | The Excel value applies, the old one is in the row history. |
| A row is missing in Excel | The entry is archived, not deleted. Bricksta never deletes anything in Excel. |
| An archived or merged entry is still in Excel | It takes no more changes. The page names it so you can remove it there. |
| “Formatted text” and billing details columns | They are not synced and can’t be mapped. |
Syncing runs through the Microsoft account of the person who connected it, while they may maintain datasets. Whoever can edit the Excel file changes the dataset. Share the file only with people who may do so.
Fill a field from a dataset
- 1Open the template and the task that should look up.
- 2Add a field and choose From dataset as its Type.
- 3Pick your dataset under Select dataset.
- 4Under Fill other fields, map columns to target fields, such as Stadt → field Stadt.

- 1Type: From dataset
- 2Select dataset
- 3Fill other fields
- 4read-only
- 5When the dataset changes
In the case, the field is a search box. Picking a row fills the field with the key and the mapped fields with the other values.
Entry missing? Add or suggest it
| Who | Sees below the matches | What happens |
|---|---|---|
| May maintain datasets | “Add “name”” | The entry is created in the dataset and fills the field right away. |
| May not | “Suggest “name”” | The field shows the name with “suggested”. The task can still be completed. |
| Customer portal and guest links | — | Neither add nor suggest. |
Open suggestions show at the top of the dataset page, and the Templates menu item shows how many. Accepting creates the entry. When rejecting, you pick a replacement or clear the field; whoever suggested it is notified.
Against duplicates in another spelling, the add entry shows “(similar: …)”, such as for “MSD GmbH” next to “MSD”. Case, punctuation and legal form don’t count here. You can still add the entry.
Protect and update values
With read-only, a target field only shows the value from the dataset, such as a list price. It shows a lock and only changes when someone picks a different row. This works for text, long text, email, number, date and yes/no.
| When the dataset changes | Effect in open cases | Default for |
|---|---|---|
| never update | The taken-over value stays. | All other fields |
| update if unchanged | Only as long as nobody changed the value in the case. | Free date fields |
| always update | Every change in the dataset reaches the case. | Read-only fields |
Deadlines that depend on an updated date are recalculated. Completed cases and tasks waiting for approval stay unchanged.
Make the choice depend on another field
Example: in a quote you first pick the customer, then only that customer’s contacts. For this, the dataset “Contacts” needs a reference column “Company” → “Customers”.
On the field “Contact”, pick the field “Customer (via “Company”)” under Only entries matching. Until a customer is chosen, it reads “Choose “Customer” first”. If the customer changes, the contact is cleared along with the fields it filled.
Special cases of the restriction
- Offered are From dataset fields of the same form whose dataset is the target of a reference column.
- Bricksta checks this on every path, including the customer portal. A contact of another company is rejected on save.
- A new entry in the restricted field belongs to the chosen company right away. Suggesting isn’t offered there.
- In a group, a sub-field can be restricted to a field at the top of the same task. Cards with their own case stay unchanged when the customer changes.
- If you change the reference column or the other field switches datasets, the restriction is dropped.
Renaming and carrying into other tasks
- The field remembers the row, not just its name. Rename a row and running cases show the new name right away.
- Completed cases and those waiting for approval keep the old name and show “today: …” below it.
- Carried on under Also in other tasks, the whole case holds one value. The field then works as an overview column, in the title and for follow-up cases.
- For a follow-up case, both fields must look up from the same dataset.
Set target and deadline for the stacked view
If you stack the case list by a field from this dataset, each stack reads its Target and deadline from its entry’s row. The target is a number column, the deadline a date column.
Unless you choose otherwise, Bricksta uses the first number and the first date column. You pick others when saving a view, under “Target and deadline”. If a row has no target, the stack shows “No target set”.
Add billing details
If a dataset holds your invoice recipients, turn on Billing details below the columns. Then you pick one column per detail, never the key column.
| Setting | What applies |
|---|---|
| Street, postcode, city, country, VAT ID | One column each. The invoice takes the recipient’s address from them. |
| Payment term in days | A number column. It applies to every order of the customer without its own term and becomes the due date. |
| Turning it off | Only possible once no column is assigned any more. |
| Changing cells and assignment | Only with the Maintain billing details right. Initially everyone who manages the organization has it. |
| Merging and deleting for good | Also only with Maintain billing details. Anyone who maintains the dataset can archive. |
| Excel sync | Leaves these columns out, in both directions. |