Oracle Field Service
Using Core Application
Chapter 2
Dispatcher Activities
Synchronization Conflicts
Offline functionality constraints may cause some conflicts during the synchronization. Conflict occurs if the changes
you have made offline contradict with the relevant changes made in Oracle Field Service in the online mode
(automatically or manually). Some examples of conflicts are as follows:
• You deactivated the route while offline, while a new activity was added to the route.
• You created an activity while offline, while the your route was deactivated.
• You started and completed an activity in the offline mode, while this activity was moved to another user or
rescheduled.
• You completed the same activity in the offline mode and set to not done in Oracle Field Service.
Resolve a Conflict
If a synchronization conflict occurs, you cannot synchronize some changes. In addition, some actions performed
in the offline mode can be rejected. In this case, the error 'Internal error. Please review your route.' is displayed. You
can view the details of the conflict and resolve it only through Oracle Field Service Core Application. You can track
synchronization conflicts in the activity history, through the 'sync error' label.
1. Log in to Oracle Field Service Core Application.
2. Click Dashboard > Offline Synchronization .
The Offline Synchronization screen is displayed. If there are no conflicts, the message, No conflicts found is
displayed. If there are any conflicts, the conflicts are displayed in a table. This screenshot shows an action that
was rejected while synchronizing; it also shows the reason for rejection:
3. Review the information in the conflict data table.
Column Description
Type The icon for the entity in which conflict has occurred:
◦
Route
◦
Activity
◦
Inventory
◦
Service request
Identifier The activity identifier in which conflict has occurred.
169
To Next Page
Loading...
Need help?
General
