Create From File

Creating a Sheet from a file you already have is one step. Drop or pick a CSV, JSON, or XLSX on /resources/create/Sheet and you arrive at a resource whose Data blade already holds the parsed rows — instead of creating an empty sheet, opening the Data blade, and running Import as a second act.

The file input is optional: name-only create works exactly as before, and every other resource type is untouched.

How it works

There is no new machinery here. The parse is the same client-side deserializer the Data blade's Import command uses, and the write is the same first saveResourceContent the blade would have done — the form just puts them in one submit.

flowchart LR
  DROP["file drop / picker on<br/>/resources/create/Sheet"] -->|"extension → DataSourceConfigurationMap"| PARSE["client parse<br/>(deserialize)"]
  PARSE --> PREV["5-row preview +<br/>name pre-filled from filename"]
  PREV -->|Create| CR["sheet.createResource"]
  CR -->|"first saveResourceContent<br/>{ settings, data }"| BLOB[("content blob")]
  BLOB --> DATA["/resources/[id]/data<br/>(rows ready)"]
  CR -->|"save failed"| OVER["/resources/[id]<br/>(valid empty sheet + error)"]

• The format comes from the file, not a picker. The drop zone accepts every extension in DataSourceConfigurationMap, and getDataSourceTypeByFileName resolves the format from the name — so a new portable format needs no change to the create form. An unsupported extension blocks Create with a message naming what is accepted.
• The filename is the name you never have to type. It pre-fills the name field (extension stripped, through normalizeString), and stays editable.
• A parse failure blocks Create, surfaced on the file field itself. The form is not partly valid: you cannot create a sheet from a file that did not parse.
• A save failure after create is not a half-written resource. createResource writes no blob, so the save is the first write, exactly as it is from the Data blade. If it fails you keep a valid, empty Sheet and see the error — never a corrupt blob.
• Success lands on the Data blade, not Overview. You came to see your rows.

Key files

Notes

• Client-side parse only, same as Import — there is no upload path, and the 1000-row dataset cap realities are identical to the Import command's.
• Only Sheet opts in. This is a per-type branch on the create form, which is the "type-specific initial settings" affordance the form already reserved — not a new framework. If more types ever want rich create forms, that is the create wizard tabs revisit trigger.
• The Home quick-create tile and the gallery tile for Sheet are unchanged — they lead to this same form; the drop zone is simply on it.