Uploading Spreadsheets and Large Files

Describing a data model in prose is hard work when you already have it in a spreadsheet. You can upload the file instead.

Where to find it

Architect Panel → Data:

• AI Builder — upload a file alongside your description

Working from a spreadsheet

Upload the workbook and the builder reads its structure — columns, types, the values that appear — and proposes datastores and fields to match. That is usually far closer to what you want than a description, because the spreadsheet already encodes decisions you would otherwise have to remember to mention.

Tidy it first

One header row, one table per sheet, no merged cells, no notes rows above the headers. A spreadsheet organised for a human reader gives a worse result than a plain rectangle of data, because the structure it infers is the structure you gave it.

Large files

Uploads are chunked, so a file can be roughly a gigabyte rather than the 64 MB a single request allows. The browser splits the file, the pieces are reassembled on the server, and — because assembling a large file is not a web request — the work happens as a background job.

The tasks involved

• Background Jobs — dispatches and reaps queued work including file assembly. Every minute.
• Document Text Extraction — indexes the contents so uploaded documents are searchable. Every fifteen minutes.

Both ship disabled under Automation → Tasks. A large upload that appears to stall at the end is usually the jobs task not running.

What not to upload

The file contents reach the AI provider. Do not upload live personal data to design a schema — a sample with realistic structure and invented values gives the same result without the disclosure.