The data sync isn’t working or is unable to complete in the Salesforce Field Service mobile app with an error - "We couldn’t complete your sync. Please try again" and below is the reference screenshot.
To resolve the data sync error or completion issue on the Salesforce Field Service mobile app, complete the following two steps:
- The first step is to collect the device logs, (Mobile App > Profile > Settings > Provide Feedback or Report an issue).
- The second step is to review the device logs and observe if you find similar errors as shown in the following scenarios.
Error in device log:
2023-02-28T14:06:02.557Z [XPLAT][ERROR] SalesforceLoader - unable to load data. Loader Name: SoqlLoader. [ERR(API_ERROR) msg: Invalid Type Exception: Isn’t a valid iKeyPrefix input api: INVALID_CROSS_REFERENCE_KEY]
2023-02-28T14:06:02.558Z [APP][ERROR] Activity error: Invalid Type Exception: Isn’t a valid iKeyPrefix input
After you find this error, then the third step is to run the below SOQL query to find any orphaned Service Appointment record available in the org as the preceding error is related to the orphaned records,
SOQL Query:
SELECT Id, ParentRecordId from ServiceAppointment where ParentRecordId=null
If you find one or more orphaned Service Appointment records in your org then please Contact Salesforce support and the Support team will be fixing this issue by running back-end scrutiny with the valid Work Order as a parent to one or more orphaned Service Appointment records.
Error in device log:
SalesforceLoader - unable to load data. Loader Name: SoqlLoader. [ERR(API_ERROR) msg:
Latitude, Longitude, Contact.Email, Contact.MobilePhone, Contact.Phone
^
ERROR at Row:1:Column:164
No such column 'MobilePhone' on entity 'Contact'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the described call for the appropriate names. api: INVALID_FIELD]
2023-07-26T20:57:26.068682Z W/ErrorHandler:
Latitude, Longitude, Contact.Email, Contact.MobilePhone, Contact.Phone
To resolve, provide "Read" access to the fields appearing in the device logs in the respective object. An example, from the above device log reference, provide "Read" access to the "MobilePhone" field on the Contact object to the affected user.
000395367

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.