Tablora · Library
Keep independent tables separate
A page can hold two separate tables with different headers or units. Keep them apart in the app and only merge tables that share a schema.
Two grids, one page
Statements, reports and price lists often put more than one table on a page: a transaction list and a fee summary, a price table and a shipping table, a balance and a breakdown underneath it. Each has its own header and often its own units. Joined into one grid, the columns line up visually but mean different things, and any sum over a joined column adds unrelated values.
Before you clean headers or normalize amounts, establish where each table starts and ends.
How the app separates tables
When the Tablora app reads a PDF page, photo or scan, it can return more than one table from the same page. Each one appears as its own chip labelled Page n · n, showing the page number and the table's position in the document, and the selected table shows its rows × columns count. The Source · page view shows the region of the page that the selected table came from, so you can check that the boundary is where you expect.
The browser tools do not read page images. If you paste text that came from a page with two tables, the inspector sees one block of rows and cannot tell where one table ends.
Keeping tables apart
- For each table chip, compare the first row with the source and confirm it carries that table's own header.
- Check units and currencies per table, not per page.
- Use Merge pages only for tables that continue each other, such as one transaction list spread over several pages.
- To keep tables apart in the file, choose All n tables, one sheet each in Export table, so each table gets its own sheet.
- If two tables did end up in one grid, for example a summary directly under a list, remove the rows that belong to the other table with Delete row and keep a note of them, or split the grid in your spreadsheet after export.
A merge caution
Merge pages decides which tables to join by column count alone. Every table with the same number of columns as the first table is appended to it, and tables with a different count are left separate. Two unrelated tables that happen to have three columns each would therefore be joined. Look at every table first and merge only when they share a schema; otherwise export them as separate sheets.
If you work in the browser with pasted text, split it into one block per table before inspecting, normalizing or checking totals, and combine results only after you have defined columns that really match.