FSM Mobile File and Image Field Behavior
File and image fields in Field Service Management (FSM) Mobile can display existing content or accept a selected value. For the capability, prerequisites, and setup links, see FSM Mobile File and Image Fields.
Displaying existing content
A read-only File or Image element displays a link when a value is available. Its link text uses the supplied file name or file ID. Opening the link uses the supplied file address. Standard relative file addresses in FSM Mobile receive the session authentication context. The browser or device determines how the file opens.
An editable File element displays the selected file name or ID and lets you select a replacement or clear the value. An editable Image element also provides an image preview, with loading and image-load error indications. Read-only image display uses a link rather than that editable preview.
A local preview can display newly selected image data before upload. A locally selected value provides a server download link only after required server processing completes and the returned mapping supplies the link.
Selecting files and capturing images
Each File or Image element holds one file value. Several elements or separately mapped table rows can hold separate values. A single element is not a multiple-attachment list.
The Image element can request camera capture when configured. The device and browser determine whether and how capture is offered. Camera configuration does not guarantee a particular camera or prevent selection of existing content.
Picker filters guide the types offered during selection. Picker filters do not enforce permitted content types or prove that NetSuite will accept the upload. For the supported filters and camera controls, see File and Image Selection and Upload Behavior.
Image processing and selection metadata
Recognized PNG, JPG or JPEG, GIF, and BMP content selected through either element follows the browser's image-processing path before upload. The standard image dimension limit is 1080 pixels for the largest dimension, preserving proportions without enlarging smaller images. An element can use a different dimension limit.
Processing depends on the browser being able to decode and render the image. It can change the stored image content. An uploaded image is not guaranteed to preserve the original encoding, animation, or embedded metadata. Selecting another format through an Image element does not cause that format to receive the image processing described above.
The selected value includes the time of selection and the FSM Mobile location coordinates when available. The standard upload path stores these values as metadata in the native file's Description. They are separate from the photograph's original capture time or embedded location, and from the Field Service File association's Geolocation field.
Replacement and clearing
Changing the element changes the proposed value. Its effect in NetSuite depends on the mapping and successful synchronization.
|
Change |
Effect Through the Standard Field Path |
Existing-File Consequence |
|---|---|---|
|
Select content for upload |
Creates a native file, writes its ID through the mapped field, and attaches the created file to the saved resource record. |
Does not overwrite or delete the previously referenced file, or detach its existing native attachments. |
|
Save a value that already identifies a native file |
Uses that file ID through the mapping. |
Does not upload another copy or automatically add an attachment through the file-creation step. |
|
Clear the value |
Supplies an empty value to the write mapping when the change is allowed and synchronizes successfully. |
Does not delete the native file or remove its existing attachments. |
An empty required File or Image value fails FSM Mobile validation. Making an element hidden, disabled, or read-only does not remove its requirements. Passing FSM Mobile validation does not prove that the file exists, can be opened, or satisfies the record rules in NetSuite.