What causes ConnectALL to skip an item?
Article ID: 379493
Updated On:
Products
Issue/Introduction
During synchronization, there are times when an item may be skipped in the Activity Monitor.
This article outlines some reasons why the item may be skipped.
Resolution
Field Direction
The direction of a synch can be controlled on a field level. If you have a field mapping that has been configured to synch in a single direction, and that field was the only item that was updated, ConnectALL will skip that work item if the updated side violates the constraint configured on the field level.
Field Level Configuration
A field can be configure to only synchronize during a create event, an update event or both. If a field is configured to only be synched when the work item is created or if the work item is updated, then ConnectALL will remove that field from its payload and the field will be skipped during the opposing event. And, if that field is the only item that ConnectALL determined needed to be synched, then there is no further work for ConnectALL to perform and the record is subsequently skipped.
Read Only Field
Read-only fields can not be updated. So, for example, if you are synchronizing a read-only work item ID field into a string field in the target system, and you make a change to that string field in the target system, those changes can not be synchronized back to the read-only field. If that field is the only field that was updated, the work item will show as skipped in the Activity Monitor.
Feedback
