Siebel CRM Desktop for IBM Notes Administration Guide > Customizing Picklists > Process of Creating Dynamic Picklists That Use Custom Objects >

Modifying Siebel CRM Desktop to Support the New Integration Object

This task is a step in Process of Creating Dynamic Picklists That Use Custom Objects.

If you expose a new object to Siebel CRM Desktop, then you must create a new type in the Ln_connector_configuration.xml file. This file defines the objects that Siebel CRM Desktop synchronizes. For more information, see Files in the Customization Package.

To modify Siebel CRM Desktop to support the new integration object

1. Use an XML editor open the Ln_connector_configuration.xml file and then add the following code:

   <type id="Fulfillment Center">
     <view label="Fulfillment Center"
     label_plural="Fulfillment Centers" small_icon="type_image:Generic:16"
     normal_icon="type_image:Generic:24"
     large_icon="type_image:Generic:48"
     suppress_sync_ui="true"></view>
     <synchronizer name_format=":[:(Name):]"
       frequency="604800" threshold="0">
       <links></links>
     </synchronizer>
   </type>

2. Create a new metadata type to support the new integration object. You use an XML editor open the siebel_meta_info.xml file and then add the following code:

   <object TypeId='Fulfillment Center' Label='Fulfillment Center' LabelPlural='Fulfillment Centers' ViewMode='All' EnableGetIDsBatching='true' IntObjName='CRMDesktopFulfillmentCenterIO' SiebMsgXmlElemName='FulfillmentCenter' SiebMsgXmlCollectionElemName='ListOfCRMDesktopFul fillmentCenterIO' >
   
   <prohibit_operation AnyMod='yes' ErrMsg='#mod_operation_is_prohibited_err_msg'/>
   
   <extra_command_options>
     <option Name='PrimaryKey1M' Value='Id' />
     <option Name='ForeignKey1M' Value='Id' />
     <option Name='Cardinality' Value='1M' />
     <option Name='ServerServiceVersion'Value='2' />
   </extra_command_options>
   
   <field Name='Conflict Id' Label='Conflict Id' DataType='DTYPE_ID' IsFilterable='no' IsHidden='yes'IOElemName='ConflictId' />
   
   <field Name='Created' Label='Created' DataType='DTYPE_DATETIME' IOElemName='Created' />
   
   <field Name='Created By' Label='Created By' DataType='DTYPE_ID' IsFilterable='no' IsHidden='yes'IOElemName='CreatedBy' />
   
   <field Name='DS Updated' Label='DS Updated' DataType='DTYPE_DATETIME' IsFilterable='no' IsHidden='yes' IsTimestamp='yes' IOElemName='DBLastUpd' />
   
   <field Name='Id' Label='Id' IsPrimaryKey='yes' DataType='DTYPE_ID' IsFilterable='no' IsHidden='yes' IsPartOfUserKey='yes' IOElemName='Id' />
   
   <field Name='Mod Id' Label='Mod Id' DataType='DTYPE_ID' IsFilterable='no' IsHidden='yes' IOElemName='ModId' />
   
   <field Name='Name' Label='Name' DataType='DTYPE_TEXT' IsPartOfUserKey='yes' IOElemName='Name' />
   
   <field Name='Updated' Label='Updated' DataType='DTYPE_DATETIME' IsHidden='yes' IOElemName='Updated' />
   
   <field Name='Updated By' Label='Updated By' DataType='DTYPE_ID' IsFilterable='no' IsHidden='yes' IOElemName='UpdatedBy' />
   </object>

3. Create the basic mapping object to support the new integration object. You use an XML editor to open the Ln_siebel_basic_mapping.xml file and then add the following code:

   <type id="Fulfillment Center">
     <field id="Name">
       <reader>
         <lotus_std>
           <lotus_field id="LastName" />
             <convertor>
               <string />
             </convertor>
         </lotus_std>
       </reader>
       <writer>
         <lotus_std>
           <lotus_field id="LastName" />
             <convertor>
               <string />
             </convertor>
         </lotus_std>
       </writer>
     </field>
   </type>

   When Siebel CRM Desktop synchronizes data it uses this code to determine where to store mapping data in IBM Notes.