Configuring FSM Mobile File and Image Fields
Configure File and Image elements under routes/mobile.<resource ID>.element. Use these elements to display existing documents or images, or to capture and upload content for a record. Configure the matching record and field mappings under that resource's article. For the capability and file lifecycle, see FSM Mobile File and Image Fields.
This topic includes the following sections:
This topic covers fields within records and resources. For information about the supplied files resource, description editing, and native-file deletion, see Configuring FSM Mobile File Management.
File and Image Field Setup Options
Choose the setup combination for your intended outcome. The following table combines the elements, mappings, record setup, and synchronization requirements. The shared references define individual properties and defaults. An element alone doesn't create a NetSuite field or save its value.
|
Intended Outcome |
Required Setup Combination |
Configuration Example |
|---|---|---|
|
Display an existing file or image |
Load the stored file reference and its accessible address into a |
|
|
Display without allowing input |
Combine element |
|
|
Upload a file into a record field |
Combine |
|
|
Capture or select a photograph |
Combine |
|
|
Generate fields from a NetSuite form |
Load the appropriate form, include the file and image fields and retain Automap or supply matching article mappings. |
|
|
Define fields explicitly |
Supply each element and its complete article mapping. Form loading is unnecessary for this alternative. |
|
|
Make the entire resource view-only |
Combine resource |
For file and image value formats and the accept, camera, downsample, and maxsize properties, see FSM Mobile Element Reference. The reference includes defaults and limits. The following examples show those controls together with the record and mapping setup for each outcome.
For form properties and permission precedence, see FSM Mobile Resource Properties Reference. For mapping syntax and Automap precedence, see FSM Searches and Field Mapping.
FSM Mobile File and Image Field Configuration Examples
The following examples are custom configuration fragments, not standard defaults or complete account configurations. Merge only the intended changes. For guidance on the shared Editor, activation, merging, and Preview, see Updating and Validating FSM Configuration.
The inspection examples use placeholder record and field IDs. Replace those IDs consistently with valid IDs from your account.
For more information, see Configuring File and Image Uploads in FSM Mobile.
For more information, see FSM Mobile File and Image Field Dependencies and Limits.
When Changes Apply
Element, form, and map changes apply when FSM Mobile loads the revised resource definition and data. Input choices such as camera, accept, and downsample affect subsequent selections. These input choices don't resize or move files already saved in NetSuite. Changing a map doesn't migrate earlier stored references or native attachments.
Saving an editable article locally and synchronizing it to NetSuite are separate stages. Successful synchronization returns the saved values used by FSM Mobile. Accessing server files and completing new uploads require a connection and the applicable permissions. For shared reload and resource-selection guidance, see Applying Resource Changes.