Uploading a document and file size limits
This article shows you how to upload a file to a record in MobilityManager and explains the rules the platform enforces, including the 50 MB size limit and the mandatory category.
Before you start
Uploading requires the documents:manage permission, typically held by FleetManager and SystemAdmin. You also need an active company (tenant) in your session, and the parent record you are attaching to must already exist.
Upload a document
- Open the record you want to attach the file to — for example a vehicle, a Beleg (receipt/expense document), a damage case, or a Strafmandat (penalty notice).
- In that record's documents area, choose the file from your device.
- Select a document category. This is required.
- Confirm the upload. The platform stores the file, records its metadata, and saves the content as version 1.
Behind the scenes the file is sent to the shared DocumentModule with the record's association type and ID, so you do not choose those values manually — they come from the record you opened.
The 50 MB size limit
Uploads are capped at 50 MB per file. This limit is enforced framework-wide on the request body, so a file above the cap is rejected by the server before it is processed. If your file is too large, reduce it first — for example, scan at a lower resolution, or split a multi-page PDF.
Tip: Photos straight from a phone camera are usually well under 50 MB, but high-resolution multi-page scans can exceed it. If an upload fails immediately with no category error, the file size is the most likely cause.
What the platform validates
| Rule | What happens if it fails |
|---|---|
| A file is selected and not empty | "File is required." |
| A category is chosen | "Please select a document category" |
| The category is an active system category | "Category is required and must match an active system document category." |
| The record type is supported | "Document operation unavailable" |
| A company context is active | "Tenant context is required for document operations." |
Category values are normalized to lowercase before they are matched, so capitalization does not matter.
Safe retries and duplicate prevention
If an upload hits a transient problem — a dropped connection, a timeout, or a temporary storage hiccup — the platform automatically retries with increasing back-off, up to five attempts. If all attempts fail, you see "Upload failed. Please retry." Validation problems (a missing category, a wrong record type) are not retried, because retrying cannot fix them.
The upload path also supports an idempotency key, which lets a repeated submission of the same request return the original result instead of creating a duplicate document. Your client handles this automatically; you do not need to set anything.
Note: A successful upload creates a new version. Uploading again does not overwrite the earlier file — it adds version 2, version 3, and so on, and downloads return the newest.
Related
- How documents work across the platform
- Supported file types
- Downloading a document
- Managing document categories
