Siebel CRM Desktop for IBM Notes Administration Guide > Customizing Picklists > Process of Creating Dynamic Picklists That Use a SalesBook Control >

Modifying the Basic Mapping and Connector Configuration

This task is a step in Process of Creating Dynamic Picklists That Use a SalesBook Control.

In this topic you modify the basic mapping and connector configuration.

To modify the basic mapping and connector configuration

1. Allow Siebel CRM Desktop to store values for the new fields you added in Step 1. You add the following code to the Fulfillment Center object in the Ln_siebel_basic_mapping.xml file. This code maps telephone number fields to existing IBM Notes fields and creates a custom field for the Description field:

   <field id="Main Phone Number">
     <reader>
       <lotus_std>
         <lotus_field id="BusinessTelephoneNumber" />
           <convertor>
             <string />
           </convertor>
       </lotus_std>
     </reader>
     <writer>
       <lotus_std>
         <lotus_field id="BusinessTelephoneNumber" />
           <convertor>
             <string />
           </convertor>
       </lotus_std>
     </writer>
     </field>
       <field id="Main Fax Number">
     <reader>
       <lotus_std>
         <lotus_field id="BusinessFaxNumber" />
           <convertor>
             <string />
           </convertor>
       </lotus_std>
     </reader>
     <writer>
       <lotus_std>
         <lotus_field id="BusinessFaxNumber" />
           <convertor>
             <string />
           </convertor>
       </lotus_std>
     </writer>
     </field>
       <field id="Description">
     <reader>
       <lotus_std>
         <lotus_field id="Description" />
           <convertor>
             <string />
           </convertor>
       </lotus_std>
     </reader>
     <writer>
       <lotus_std>
         <lotus_field id="Description" />
           <convertor>
             <string />
           </convertor>
       </lotus_std>
     </writer>
   </field>

2. Locate the following type definition for the opportunity object:

   <type id="Opportunity"

3. Add the following code to the object you located in Step 2:

   <field id="JVD Fulfillment Center Id">
     <reader>
       <lotus_std>
         <lotus_field id="JVDFulfillmentCenterID" />
           <convertor>
             <binary_hexstring />
           </convertor>
       </lotus_std>
     </reader>
     <writer>
       <multiwriter>
         <lotus_field id="JVDFulfillmentCenterID" />
           <linked_fields>
             <link src_field="Name" dest_field="JVD Fulfillment Center">
               <lotus_std>
                 <convertor>
                   <string />
                 </convertor>
               </lotus_std>
             </link>
           </linked_fields>
       </multiwriter>
     </writer>
   </field>

   The writer statement in this code includes a link field that allows CRM Desktop to get the value for the JVD Fulfillment Center field in the Opportunity object from the Name field of the Fulfillment Center object. This is similar to how Siebel CRM uses a pick map. If Siebel CRM gets values for multiple fields through a join, then you can add multiple fields in the link_fields section. These link_fields must exist in the basic mapping but you do not need to add them to the metadata.

4. Use an XML editor open the Ln_connector_configuration.xml file.
5. Locate the following definition for the Opportunity object:

   <type id="Opportunity"

6. Add the following code to the definition you located in Step 5:

   <link>JVD Fulfillment Center Id</link>

   This code specifies the JVD Fulfillment Center Id field as a link on the Opportunity object. In the metadata you specify that the JVD Fulfillment Center Id field is related to another object in CRM Desktop. CRM Desktop uses that relation during synchronization.