Siebel CRM Desktop for IBM Notes Administration Guide > Controlling Synchronization > Controlling Other Configurations That Affect Synchronization >

Controlling the View Mode During Synchronization According to Object Type

This topic describes how to control the view mode that Siebel CRM Desktop uses during synchronization for an object type. The view modes that are configured in the client application metadata affect data access. You can configure each synchronization object with a different level of data access. This configuration is implemented as a view mode argument that CRM Desktop passes to the EAI Siebel Adapter business service during synchronization. It establishes basic access control in the client.

For example, data about opportunities is available to the sales representatives who are on the team for the opportunity. The default configuration for CRM Desktop specifies that the opportunity synchronization object must use the sales representative view mode. Several view mode arguments are available. For example, All, Organization, Sales Rep, or Personal. For more information, see About the EAI Siebel Adapter Business Service.

To control the view mode during synchronization according to object type

1. Use an XML editor open the siebel_meta_info.xml file.
2. Locate the type tag of the object that must use a view mode during synchronization.

   For example, locate the following tag:

   object TypeId='Account.Account_Note'

3. Locate the viewmodes subelement of the type tag you located in Step 2.
4. Set the viewmodes subelement using the following format:

   viewmodes view_mode_context1="view_mode_value" view_mode_context2="view_mode_value" view_mode_context3="view_mode_value"

   where:

   • view_mode_context is set to one of the following values:
     • General. Requests server records of synchronized object types that match the user synchronization filters with master filter restrictions applied. If you specify this value, then it overrides the value in the viewmode attribute. For more information, see Step 2.
     • Dedup. Detects duplicate records when CRM Desktop must add records to IBM Notes or to the server database. If you do not specify this value, then it sets the value for the Deduplication view mode to the value that you set for the General view mode. For more information, see Resolving Synchronization Conflicts.
     • QBID. (Query By Id) Requests objects that CRM Desktop must synchronize to IBM Notes to maintain referential integrity because this object is related to a synchronized record. It requests this object even if the object does not match a user synchronization filter. You must specify a Query by Id for each object type that CRM Desktop queries by Id. The default value is All.
   • view_mode_value is set to one of the following values:
     • All
     • Sales Rep
     • Personal
     • Organization

       For example:

   viewmodes General="Organization" Dedup="All"

Example That Controls the View Mode During Synchronization According to Object Type

The following code controls the view mode that Siebel CRM Desktop uses during synchronization for the Account.Account_Note object type:

<object TypeId='Account.Account_Note' Label='#obj_account_note' LabelPlural='#obj_account_note_plural' EnableGetIDsBatching='true' IntObjName='CRMDesktopAccountIO' SiebMsgXmlElemName='AccountNote' SiebMsgXmlCollectionElemName='ListOfAccountNote' >
  <viewmodes General="Organization" Dedup="All" />
  <open_with_url_tmpl>
    <![CDATA[
      :[:(protocol):]://:[:(hostname):]::[:(port):]/sales/:[:(lang):]/?SWECmd=GotoView&SWEView=Account+Note+View&SWERF=1&SWEHo=:[:(hostname):]&SWEBU=1&SWEApplet0=Account+Entry+Applet&SWERowId0=:[:(parent_id):]&SWEApplet1=Account+Note+Applet&SWERowId1=:[:(own_id):]
    ]]>
  </open_with_url_tmpl>
  <extra_command_options>
    <option Name='PrimaryKey1M' Value='Id' />
    <option Name='ForeignKey1M' Value='Account Id' />
    <option Name='Cardinality' Value='1M' />
    <option Name='ServerServiceVersion' Value='2' />
  </extra_command_options>
  <field Name='Account Id' Label='Account Id' DataType='DTYPE_ID' IsNullable='no' IsFilterable='no' IsRefObjId='yes' RefObjTypeId='Account' RefObjIsParent='yes' IsPartOfUserKey='yes' IOElemName='AccountId' />
  <field Name='Conflict Id' Label='Conflict Id' DataType='DTYPE_ID'
IsFilterable='no' IsHidden='yes' IOElemName='ConflictId' />
  <field Name='Created' Label='#fld_account_account_note@created' DataType='DTYPE_DATETIME' IsPartOfUserKey='yes' IOElemName='Created' />
  <field Name='Created By' Label='Created By' DataType='DTYPE_ID' IsFilterable='no' IsRefObjId='yes' RefObjTypeId='Employee' IOElemName='CreatedBy' />
  <field Name='Created By Name' Label='#fld_account_account_note@created_by_name' DataType='DTYPE_TEXT' IOElemName='CreatedByName' />
  <field Name='Created Date' Label='Created Date' DataType='DTYPE_UTCDATETIME' IsHidden='yes' IOElemName='CreatedDate' />
  <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='Note' Label='#fld_account_account_note@note' DataType='DTYPE_NOTE' IOElemName='Note' />
  <field Name='Note Type' Label='#fld_account_account_note@note_type' DataType='DTYPE_TEXT' HasPicklist='yes' PicklistIsStatic='yes' PicklistCollectionType='FS_NOTE_TYPE' PicklistTypeId='List_Of_Values' IOElemName='NoteType' />
  <field Name='Private' Label='Private' DataType='DTYPE_BOOL' IsHidden='yes' IOElemName='Private' />
  <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>