Upload files actions
Stream evidence and bulk returns to the file store your organisation uses. Choose Page actions → Upload files (previously Site upload/SharePoint upload) to send answer attachments, ordinary uploads or Bulk Data files to Govform storage, SharePoint, AWS S3, Google Cloud Storage or Azure Blob Storage.
Select the destination
Choose a configured Library connection and destination folder. QA and Production use their own settings. Govform storage provides a managed destination; your own store gives you control of its permissions, retention and lifecycle policy.
Configure file types, maximum size and antivirus/CDR at the incoming file component. This action transfers an existing stored file; it does not apply a new component scan or reconstruction step. Choose upload limits and protection.
Select the file and evidence version
For corrected bulk answers, select the Bulk Data component, rather than its linked upload field. Choose the evidence and artifact explicitly:
| Choice | Options | Result |
|---|---|---|
| Evidence version | Current confirmed (default), first-submitted, or a specific submitted revision. | Submitted revisions are Response history versions, not intermediate dataset edits. First-submitted means revision 1. |
| File | Validated CSV (default) or untouched source upload. | The CSV includes confirmed corrections; the source remains separate and can contain the original errors. |
| Repeating component | Zero-based repeat row. | Select the dataset belonging to the intended repeated record. |
Historical selections require retained Response history and their stored files. Missing evidence fails rather than silently selecting a different version. Each upload row can choose a different revision.
Set filename and timing
- Enter the destination filename without an extension. Govform adds
.csvfor validated data or the source file’s original extension. - Use Liquid where needed, for example
bulk-{{ form.submissionId }}. - Use distinct filenames when preserving separate exported revisions.
- Run after the respondent confirms their data. Historical selection must wait until the required Response history revision exists.
Existing action triggers and post-submission workflows apply. Test real files in QA and confirm the destination, filename and selected evidence.
Stream large files instead of embedding them
Transfers stream through the configured store and do not consume the 25 MiB combined raw-file allowance for Base64 API bodies. Original uploads have a 20 GB ceiling, with a 10 MB default component limit; scanning, CDR and store policies can reduce the input size. Transfer provider and execution limits still apply.
Bulk Data processes up to five million data cells and 200 configured columns before confirmation. The generated validated CSV is distinct from the original upload. You can also stream selected bulk artifacts through the authenticated API for an external processor.
This action delivers files. Creating one SharePoint list item per CSV row requires an external row-processing integration; the ordinary list-item action is not a bulk importer.