The submission of appointments to Dataforce ASAP are split into three stages. These stages can be seen from the displayed loading bar.

• 0 to 20% on the loading bar indicator means that Dataforce Runabout is sending the appointment data such as question answers, customer details, signatures, photo meta-data etc to the Dataforce ASAP server.
• 20 to 80% on the loading bar indicator means that Dataforce Runabout is uploading photos
• 80 to 100% on the loading bar indicator means that Dataforce Runabout has completed uploading the appointment and is now downloading the updated scheduled for the day.

If the process is stuck at 20% it could mean that the image upload has stopped or so slow it seems that it is not moving.

The potential origin of this issue might be because of your internet connection speed.

You can try to run google speed test to check your upload speed.

Please click here to run google speed test.

If internet connection speed is the problem then try to move to an area with better reception or alternatively connect to a wifi hotspot.

Common Error: Appointment Modification Conflict

Issue Description

In the SaaS application used by fieldworkers, a common error may occur when a fieldworker attempts to modify an appointment on the mobile app that has been concurrently modified by another user in the backend. This error is triggered to prevent conflicting changes and data inconsistencies. The error message, “Appointment X has been modified by another user and cannot be synced at this time,” informs the fieldworker about the conflict and provides three options for resolution.

Symptoms

Error message: “Appointment X has been modified by another user and cannot be synced at this time.” Inability to sync the appointment with the backend database. Options displayed to address the conflict: remove from next sync, enable ‘Allow Overwrite,’ or delete from the device.

Resolution Options

When encountering the appointment modification conflict error, the fieldworker is presented with three options:

1. Remove the Appointment from the Next Sync

To remove the appointment from the next sync, follow these steps:

1. Locate the appointment in question within the mobile app.
2. Click the menu icon (3 dots) associated with the appointment.
3. Select the option “Remove from Next Sync.”
4. The appointment will be excluded from the upcoming synchronization process.

Please note, your unsynched changes will be retained, but the appointment will not be synced. This allows changes in other appointments to be synced without being blocked by this appointment.

2. Ask an Administrator to Enable ‘Allow Overwrite’

If the fieldworker believes their modifications should take precedence over the changes made by another user in the backend, they can request an administrator to enable the ‘Allow Overwrite’ option for this appointment. Follow these steps:

1. Contact your system administrator or relevant support personnel.
2. Provide them with the details of the appointment (Appointment X) and the error message received.
3. Request them to enable the ‘Allow Overwrite’ setting for the appointment.
4. Once the setting is enabled, attempt to sync the appointment again. Please exercise caution when using the ‘Allow Overwrite’ option, as it may lead to data inconsistencies if conflicting changes are not appropriately resolved.

3. Delete the Appointment from Your Device

If the modifications made by another user in the backend are deemed more important or accurate, the fieldworker can choose to delete the appointment from their device. To delete the appointment, follow these steps:

1. Locate the appointment in question within the mobile app.
2. Click the menu icon (3 dots) associated with the appointment.
3. Select the option “Delete from Device.”

4. Confirm the deletion when prompted. By choosing this option, the appointment will be removed from the fieldworker’s device, and any unsynchronized changes to the appointment will be lost.

5. The appointment will be redownloaded to the fieldworkers device the next time they sync.

Prevention and Best Practices

To avoid encountering the appointment modification conflict error, it is recommended to follow these best practices:

Always perform a sync before making any modifications to an appointment. This ensures that you have the latest data and reduces the chances of conflicts. Communicate with other users or administrators involved in appointment management to minimize simultaneous modifications. If multiple users need to work on the same appointment, establish a clear workflow or communication process to coordinate changes effectively. Regularly sync your mobile app to update the appointments and changes made by other users in the backend. By adhering to these best practices, you can minimize the occurrence of conflicts and maintain data integrity within the SaaS application.

Conclusion

The appointment modification conflict error can occur when a fieldworker attempts to modify an appointment on the mobile app that has been modified by another user in the backend. By understanding the provided error message and following the appropriate resolution options, fieldworkers can effectively address the conflict and ensure the accurate synchronization of appointment data. Adhering to prevention best practices will help minimize the occurrence of this

Ensure that your mobile device pass the Operating Systems requirement, 4.1+ for Android or 10+ for iOS.
Follow this guide to check which OS version your mobile device runs.

In addition to OS requirement, your device will also requires internet connection, camera and location features.
Please check the following guide to enable location feature on your mobile device.

To download Dataforce Runabout on android please read to the following help page Dataforce Runabout Android Installation, and for iOS, Runabout iOS Installation.

To find the version please read to the following help page Dataforce Runabout Check the Installed Version.