Bookshelf Home | Contents | Index | Search | PDF |
Siebel Sales 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:
- A record is logged that indicates the insert failed, and synchronization continues. This is the default insert behavior. If it is enabled, the Handheld Sync Journal can be used to recover the data.
- The insert failure is logged, including details of the failure, and synchronization is interrupted. This is the extended insert behavior. Extended insert behavior guarantees that, should an insert fail, data loss does not occur since synchronization is stopped until the circumstances causing the failure are resolved.
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:
- Configuration file parameter
The configuration file parameter applies globally throughout the application. When enabled, every failed insert interrupts synchronization. The parameter is set as follows:
DefaultHandheldInsertMode=Mode
Table 15 shows the settings for this parameter.
- Business component user property
The user property is defined on specific business components. The setting in the business component takes precedence over the configuration file setting. The syntax for setting the Extended Insert on a business component and the parameter values (Table 16) follow:
HandheldInsertFailMode=Mode
Table 17 shows the combined effect of the setting in the configuration file and the setting on a business component.
- The business component setting always takes precedence over the setting in the configuration file.
- If there is no setting on a particular business component, the configuration file setting applies.
- If there is no setting in either the configuration file or on the business component, the default behavior is for Extended Insert to be disabled.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Sales Handheld Guide for Windows-Powered Devices Published: 18 July 2003 |