Siebel eConsumer Goods Handheld Guide for Windows-Powered Devices > Synchronization Conflict Handling and Recovery > Preventing Synchronization Transaction Conflicts >

Extended Insert Processing


When the server executes an insert transaction and the insert fails, there are two ways the insert failure can be handled:

NOTE:  If Extended Insert processing takes place, synchronization is interrupted. The synchronization process will continue to fail until the problem is resolved. End users will need to contact their system administrators to recover from the failure. The recovery effort may involve modifying transactions queued for processing, modifying data on the server, or reentering transactions through the handheld application.

Enabling Extended Insert Processing

You can enable Extended Insert processing in two ways:

Table 17.  Configuration File Setting
Configuration File Parameter
Mode Value
Description
DefaultHandheldInsertMode
NoFail
Disables Extended Insert processing. This is the default behavior if the parameter is not specified in the .cfg file.
FailOnError
Enables Extended Insert processing.

Table 18.  Business Component User Property Parameter
Business Component User Property
Parameter
 
Value
Description
HandheldInsertFailMode
Mode
NoFail
Disables Extended Insert processing.
FailOnError
Enables Extended Insert processing.

Table 19 shows the combined effect of the setting in the configuration file and the setting on a business component.

Table 19.  Combined Effect of Extended Insert Settings
Business Component Setting
HandheldInsertFailMode=
Configuration File Setting
DefaultHandheldInsertMode=
 
NoFail
FailOnError
No Setting in .cfg File
NoFail
NoFail
NoFail
NoFail
FailOnError
FailOnError
FailOnError
FailOnError
No Setting on Business Component
NoFail
FailOnError
NoFail


 Siebel eConsumer Goods Handheld Guide for Windows-Powered Devices 
 Published: 18 July 2003