Skip to main content

Hi all,

I'm currently testing the new Data Capture feature in the Salesforce Field Service Mobile App, specifically the upcoming Summer '25 enhancement that allows launching a Data Capture flow directly from a Work Step. 

 

According to the Summer 25 release note: 

 "Launch Data Capture forms directly from work steps to streamline your work plans… After you create your Data Capture flow, go to the work step from which you want to launch your Data Capture form. Select a flow from the dropdown list on the Action Definition field… The form auto-saves, and the status of the work step is updated automatically."  

 

My setup:

  • I have configured a Work Step with a valid and active Data Capture Flow.
  • The flow is correctly referenced via the Action Definition field on the Work Step.
  • I’m using the iOS Beta version 256.0.2 (Build #25602) of the Field Service Mobile App (via TestFlight).
  • Our Sandbox is Preview on Summer 25
  • I can launch the data capture flow from the "forms" tab without problems

Issue:

 

 When I attempt to 

complete the Work Step

, I receive the following error: 

 

 "Only field service mobile flow type is supported in the mobile app. Contact your Salesforce admin."  

 

Has anyone in the community managed to get this working yet? Or any insights from your end @Kunal Borde would be greatly appreciated as I cannot find any documentation about this online yet.

 

Thanks heaps! 

 

Launching Data Capture Flow from Work Step in Field Service Mobile (iOS, Beta 256.0.2) - Summer 25 not working?

6 respostas
  1. 3 de jul. de 2025, 21:49

    @Kara Carreri The issue stemmed from a newly introduced standard field on the Work Step object—'Process Type' —which had no Field Level Security configured by default. As a result, no profiles (not even Administrators) had visibility into the field. 

     

    Once we made the field visible for the relevant profiles and updated to Field Service Mobile App v256, data capture forms could be launched from a Work Step. 

     

    Unfortunately, this change wasn’t documented in the release notes or official help articles, which made the troubleshooting more difficult than necessary.

0/9000