Purpose
Supports legacy flows with a separate upload dialog. The block runs in an already saved flow but cannot be added, copied or pasted into new ones. For a new flow, use “File” from File Manager with “Ask the user for an updated file”.
Inputs and outputs
With at_start=true, there is no input. Within a branch, it has in, but the uploaded table replaces the input data; out contains the file that was read.
Parameters
| Parameter | Settings and values | Options and limits |
|---|---|---|
at_start | Open the upload at the start of a branch without an input connection. | Default: enabled |
sheet | The workbook’s worksheet name. | Default: emptyUp to 256 characters |
range | A cell range in A1 notation, for example A1:F500. | Default: A1:M100Up to 40 characters |
header | Treat the first row of the range as field names. | Default: enabled |
delimiter | The text file’s field delimiter. | Options: ;, ,, tab, |Default: ; |
wizard | Show the block as a step in the execution wizard. | Default: enabled |
Step-by-step configuration
- Open an existing flow containing this block.
- Check the at_start position and reading range, worksheet, headers and delimiter.
- For further development, register the file in File Manager and replace the block with a current file source.
- Transfer the connections and check that the same headings appear in a simulation.
Rules and diagnostics
- The block requires a manual upload and is therefore unsuitable for unattended execution.
- An empty worksheet value means the workbook’s first sheet.
- An inactive route does not open the dialog.
- When placed in the middle of a branch, the previous table is not appended to the new file.
Configuration example
In a legacy flow, set sheet=Sales, range=A1:F1000, header=true. The upload replaces the previous step’s table with data from this worksheet. For a new design, use the “File” block with an update request.