#Salesforce Field Service42 utenti parlano di questo argomento

Hi everyone,

I’m working on a custom LWC in Salesforce Field Service Mobile and have two related requirements.

1. Trigger LWC JavaScript when Standard Data Sync runs

I have a Work Order in Field Service, and based on that Work Order I need to fetch dynamic data from an external API.

My current flow is roughly:

Work Order → LWC → External API → Build data packet → Download packet → Store in IndexedDB

I would like to know if there is any supported way to trigger/execute my LWC JavaScript automatically when Field Service Mobile’s standard offline data sync runs or completes.

For example:

Field Service Standard Data Sync

          ↓

      Work Order synced

          ↓

   Trigger my LWC JS

          ↓

 Start external API process

Is there a supported Field Service Mobile event, hook, callback, or extension point that allows an LWC JavaScript process to be triggered by the standard data sync?

I am specifically looking for a solution using LWC/JavaScript, without requiring a native SDK if possible.

2. Continue processing when the user closes Field Service Mobile

The external API takes some time to build the data packet. Once the packet is ready, my LWC downloads it and stores it in IndexedDB for offline use.

The problem is that the API processing/download can take a significant amount of time.

Ideally I want:

User starts sync

      ↓

API starts building packet

      ↓

User closes/minimizes Field Service Mobile

      ↓

API continues processing

      ↓

Packet becomes available

      ↓

Packet is downloaded/stored

      ↓

User opens Field Service again

      ↓

LWC detects that the data is ready

I understand that an LWC/Web Worker cannot necessarily remain alive after the mobile application is completely closed, but I’m wondering if there is any Field Service Mobile-specific mechanism that can support this use case.

I have considered using a Web Worker for the API polling/download process, but I understand that a Web Worker is still subject to the mobile WebView lifecycle and may be terminated when the application is closed or suspended.

Questions

1. Is there a supported way to hook into Field Service Mobile Standard Data Sync from an LWC?
2. Can an LWC JavaScript process be triggered automatically when offline sync completes?
3. Is there any supported mechanism for executing JavaScript/background processing when the Field Service Mobile app is closed?
4. Can a Web Worker be used reliably for this scenario?
5. Is there a recommended Field Service Mobile architecture for downloading external API data into IndexedDB based on Work Order data?

Any guidance or examples would be greatly appreciated.

@* Salesforce Developers * @* Salesforce Field Service * 

Hi everyone, 

We are experiencing an intermittent issue when generating reports in Salesforce.

Sometimes, when a user tries to run/generate a report, Salesforce displays the following error message: 

Has anyone experienced a similar issue recently?

Based on the Field Service Guide, our understanding is that if a Resource Absence is created without an address, it will calculate drive time for surrounding Service Appointments using the address on the Service Territory Member for the Service Resource. 

"If an absence doesn’t have an address, optimization uses the resource’s home base to calculate travel time to the next service appointment. For a more precise travel estimate, add an address to the absence, such as the location of the previous appointment or an address for the break."

We have been seeing examples where this is not the case. Below are screenshots showing the drive time for an Absence without an address versus the drive time when it's been updated with the Service Resource's home base.

Absence without an address:

Absence with the Service Resource's home address:

Updating the Absence with the address of the previous Service Appointment does not change drive time. Confirming that, without an address, the drive time for the Service Appointment following the Absence is being calculated using the address of the Service Appointment before the Absence.

Curious if there is something we are missing or if our understanding is incorrect.

Thanks!

Hi all,

I'm trying to use Maintenance Plans, specifically the "Generate on a floating schedule" functionality. My understanding is that this should allow the system to reschedule subsequent Work Orders based on the completion date of the previous one.

Here is my scenario and what I am trying to achieve:

• I set the frequency to every 30 days (on the Maintenance Work Rule, linked to the Maintenance Asset).
• The first Work Order (WO-1) is scheduled for November 15.
• The next Work Order (WO-2) is therefore initially planned for December 15.

My expectation (the "floating" logic):

• Scenario A: If I complete WO-1 early on November 10, the next Work Order (WO-2) should be automatically rescheduled for December 10 (30 days after the new completion date).
• Scenario B: If I complete WO-1 late on November 20, the next Work Order (WO-2) should be rescheduled for December 20.

The Problem: I have run several tests, but it seems that the SuggestedMaintenanceDate on the next Work Order never gets updated. It always stays at the original December 15 date, regardless of when I complete the first Work Order.

My Questions:

1. What configuration am I missing to make this floating schedule logic work correctly?
2. Which specific DateTime field on the completed Work Order does the system use to trigger this recalculation? Is it the EndDate on the Work Order object, or the ActualEndTime from the related Service Appointment?

Thanks so much for your help,  Salvatore

@* Salesforce Field Service *