FSM Mobile accept Property for File and Image Elements
In Field Service Management (FSM) Mobile, use the accept property to filter the file types shown in the device's file picker. Configure accept as a comma-separated string of file extensions or MIME-type specifiers. For example:
The downsample property is independent of accept. It down-samples only PNG, JPG/JPEG, GIF, and BMP uploads. It doesn't convert other image formats.
{
"name": "attachment",
"type": "file",
"accept": ".pdf,.docx,.xlsx"
}
{
"name": "photo",
"type": "image",
"accept": ".jpg,.jpeg,.png"
}
|
Element type |
Default picker filter |
Effect of an explicit |
|---|---|---|
|
|
No filter. |
Replaces the no-filter default with the configured picker filter. |
|
|
|
Replaces the default picker filter when the user selects an existing file. If |
Important: accept filters the browser file picker only. It is not an upload validation rule. Depending on the device and browser, a user can still select a file that is outside the configured or default filter. FSM Mobile does not validate the selected file against accept before it displays the file in the element or sends it for upload. Configure accept to guide users, but do not rely on it to prevent unsupported file types from reaching the upload process.
WebP images: This limitation can affect .webp files even when accept is not configured. .webp is outside the default Image picker filter, but a device or browser can still return a WebP file to the Image element. FSM Mobile then displays and uploads the file without conversion or image-specific processing. The File Cabinet upload path has no WebP type mapping and falls back to MISCBINARY; the upload can therefore fail with an invalid MISCBINARY file type. Supporting WebP requires a product or integration change that converts the image or maps it to a supported File Cabinet type.