Siebel CRM Desktop for IBM Notes Administration Guide > Controlling Synchronization > Resolving Synchronization Conflicts >

Configuring Siebel CRM Desktop to Resolve Synchronization Conflicts

This topic describes how to configure Siebel CRM Desktop to resolve synchronization conflicts.

To configure Siebel CRM Desktop to resolve synchronization conflicts

1. Use a JavaScript editor to open the autoresolver.js file.
2. Navigate to the following section:

   //Opportunity

3. Add the following code:

   ar_manager.add_rule({ type: "object_type", field: " field_ID ", resolution_fn: ar_helpers.resolution_resolve_to("source", boolean) });

   where:

   • ar_manager. Is the Auto Resolver manager. It is an interface to the C++ code that CRM Desktop runs to resolve the conflict.
   • add_rule. Is the C++ method that ar_manager sends to the C++ code.
   • type. Identifies the object type where CRM Desktop applies the rule.
   • field. Identifies the field that contains the data that CRM Desktop uses to resolve the conflict.
   • resolution_fn. Identifies the rule function that CRM Desktop passes to the C++ code. This function returns a string value that indicates if the Auto Resolver resolved the conflict.
   • resolution_resolve_to. Defines the rule. The rule is configured in the autoresolve_helpers.js file. It includes the following values:
     • source is remote or local, where remote is the Siebel Server and local is the client. It identifies the source that CRM Desktop uses to resolve the conflict.
     • boolean is true or false.

       For example:

   ar_manager.add_rule({type: "Opportunity", field: " Account Id ", resolution_fn: ar_helpers.resolution_resolve_to("local", true)});

   In this example, if a synchronization conflict exists in the Account field of the Opportunity form, then this rule uses the value in the Account field from the client database as the permanent value only if the resolution_fn returns the following value:

   local

   For example:

   ar_manager.add_rule({ type: "Opportunity", field: " Account Id ", resolution_fn: ar_helpers.resolution_resolve_to("local", false) });

   In this example, if no values exists for this field on the client, then the Auto Resolver does not apply a resolution.

   For another example, you add the following code to the //Opportunity section:

   ar_manager.add_rule({ type:"Action", field:"Email To Line", resolution_fn: ar_helper.resolution_resolve_to("local", false) });