Tablora · Library
Preserve a code that resembles a date
A code such as JAN1 can be mistaken for a date when opened in a spreadsheet. Export it as an explicit text cell so the letters and digits survive.
Codes that look like calendar dates
Shelf positions, batch labels, plan names and short product codes are often built from a month abbreviation and a number: JAN1, MAR15, SEP2. Open a CSV containing them in a spreadsheet and the program may guess that they are dates, then show a day and month in your own locale's format. Once that happens, the original characters are no longer in the cell, and changing the cell format afterwards does not bring them back.
The text-safe converter avoids the guess altogether. It writes every cell of the workbook as an explicit text cell, so JAN1 arrives in the spreadsheet as the four characters J, A, N and 1.
Producing a text-safe workbook
- Paste the table into Table text and choose the Delimiter that matches your data.
- Press Calculate and check the preview: the code column should show JAN1 exactly as in the source.
- Use Download (XLSX) to get tablora-table.xlsx, and open that file rather than a CSV copy of the same data.
- If the column really holds dates, keep the text version and do a separate, reviewed date conversion in your spreadsheet.
- Check the other columns in the preview too. Codes such as 000123 or long reference numbers in the same table are protected by the same text-only export.
The JAN1 example
The page example has a single column named code with one value, JAN1. The expected cell text in the workbook is JAN1, stored as an explicit text cell, not as a formula and not as a number or date. The tool does not add a year, apply a month order, or decide whether the code was meant as a date at all.
A neighbouring code such as JAN12 or JUN30 is handled exactly the same way, because the converter never looks at the pattern of the characters at all.
What text-only cells cost you
Because every cell in this workbook is text, amounts in other columns will not sum until you convert them in the spreadsheet. If you need both safe codes and working numbers, normalize the amount column first with the numeric normalizer and treat the converted numbers as a separate step, or convert them inside the spreadsheet after import.
In the Tablora app, the XLSX export keeps a cell like JAN1 as text and turns only cells in recognized number columns into numbers. The app's CSV export writes each cell as it was read, which means the program that opens the CSV decides how to interpret it. For codes like these, the XLSX is the safer choice.
Original synthetic example
- Input
- code JAN1
- Expected cell text
- JAN1
- Cell storage
- Explicit text, not a formula or numeric cell