FSM Mobile Files Tab Selection and Upload Folders
Field Service Management (FSM) uses job, employee, and Asset context to organize uploads and select files in the FSM Mobile Files tab. For the feature overview, see FSM Mobile Files Tab.
For configuration, see Configuring FSM Mobile File Management.
Uploads use the current job and the requested Asset, or the job's Asset when no separate Asset is requested. A child Asset context selects files for that Asset. The selection does not automatically include files for every parent and child Asset.
The supplied upload root is /Field Service Management/upload/. FSM creates or uses a folder beneath it with this default naming pattern:
/Field Service Management/upload/<event-id>-<asset-id>-<employee-id>/
The following table describes each component of the default folder name.
|
Folder Component |
Default Source |
|---|---|
|
|
The current FSM Mobile event ID, which combines the record type and internal ID. For example, |
|
|
The Asset requested by the resource instance, otherwise the current job's Asset. This component is empty when neither is supplied. |
|
|
The uploading FSM Mobile employee's internal ID. |
For example, a CRM Task with internal ID 1234, Asset 5678, and uploading employee 9012 uses /Field Service Management/upload/task-1234-5678-9012/. The folder groups uploads. It does not create an Asset field on the native file or replace the task attachment relationship.
For list matching, the default map takes the Asset from a folder whose name matches the current event and employee. Otherwise, it supplies the current job's Asset. Existing task attachments without a matching folder use the job's Asset context. These attachments are not automatically classified under every child Asset.
The standard native attachment lookup uses the current event's file join. CRM Tasks provide this lookup. The supplied source identifies a limitation with the equivalent join for Project Tasks: do not expect all files attached elsewhere to a Project Task to appear through that lookup. FSM uploads can still be selected through their upload-folder context.