Oracle CRM On Demand Desktop Administration Guide > Customizing Oracle CRM On Demand Desktop > Process of Enabling Custom Object Synchronization in Oracle CRM On Demand Desktop >

Defining the Custom Object

This topic describes how to define the object name and field names for the object called Custom Object 1. The object name and field names are the same as those saved in the WDSL file for Custom Object 1.

This task is a step in Process of Enabling Custom Object Synchronization in Oracle CRM On Demand Desktop.

To define the custom object

1. Using an XML editor, open the od_meta_info.xml file.
2. Locate the following <SiebelMetaInfo> XML element.:

   <SiebelMetaInfo>
   ...
   ...
   <object TypeId='Custom Object 1' Label='CustomObject1' LabelPlural='CustomObject1' ViewMode='Sales Rep' IntObjName='Custom Object 1' SiebMsgXmlElemName='CustomObject1' SiebMsgXmlCollectionElemName='ListOfCustomObject1'>
   </object>
   </SiebelMetaInfo>

3. Update the following attributes in the <object> XML element with your custom object values:
   • TypeId='Custom Object 1'. The unique identifier of the object defined in the od_meta_info.xml file. The TypeId='Custom Object 1' attribute must have the same value as the IntObjName='Custom Object 1' attribute in the od_meta_info.xml file.
   • IntObjName='Custom Object 1'. The name of the integration object that Oracle CRM On Demand Desktop uses for requests. The IntObjName='Custom Object 1' attribute must have the same value as the TypeId='Custom Object 1' attribute.

     NOTE:  For Custom Objects 1, 2, and 3, there is a space between the words in the IntObjName value, for example, Custom Object 1 or Custom Object 2, but for Custom Object 4 and custom objects with higher numbers, they are declared as one word, CustomObject4.

   • SiebMsgXmlElemName='CustomObject1'. The XML element of the object, which is declared in the "Custom Object 1" WSDL for Oracle CRM On Demand Web Services v2.0.
   • SiebMsgXmlCollectionElemName='ListOfCustomObject1'. The name of the collection XML element as declared in the "Custom Object WSDL for CRM OD Web Services v2.0.
4. Locate the following <object> element:

   <object TypeId='Custom Object 1' Label='CustomObject1' LabelPlural='CustomObject1' ViewMode='Sales Rep' IntObjName='Custom Object 1' SiebMsgXmlElemName='CustomObject1' SiebMsgXmlCollectionElemName='ListOfCustomObject1'>
     <field Name='CreatedBy' Label='CreatedBy' DataType='DTYPE_TEXT' IsHidden="yes"/>
     <field Name='CreatedById' Label='CreatedById' DataType='DTYPE_ID' IsRefObjId="yes" RefObjTypeId="User" IsHidden="yes"/>
   <field Name='CreatedDate' Label='CreatedDate' DataType='DTYPE_UTCDATETIME' IsHidden="yes"/>
   </object>

5. Update the following Oracle CRM On Demand Desktop system fields as hidden fields for Microsoft Outlook:
   • Name='CreatedById'. The name of a field as declared in the "Custom Object 1" WSDL for CRM OD Web Services v2.0.
   • IsHidden="yes". This attribute indicates that the Oracle CRM On Demand Desktop system fields are hidden fields for Microsoft Outlook.
   • 'CreatedById' field. The foreign key field that points to the User object in Oracle CRM On Demand Desktop.
   • IsRefObjId="yes". This <field> element attribute indicates that the CreatedById field is a foreign key field in Oracle CRM On Demand Desktop.
   • RefObjTypeId="User". This <field> element attribute indicates the name of the object type to which the CreatedById field points.
6. Locate the <object> element that you want to synchronize between Oracle CRM On Demand Desktop and Microsoft Outlook.
7. Update the following Custom Object 1 fields:

   <field Name='Id' Label='Id' DataType='DTYPE_ID' IsPrimaryKey='yes' />
   <field Name='Name' Label='Name' DataType='DTYPE_TEXT' />
   <field Name='Description' Label='Description' DataType='DTYPE_TEXT' />

   When the value for the IsPrimaryKey attribute is Yes, it indicates that this field is the primary key field for the object. For more information on the attributes defined in the <field> XML element, see Field Element of the od_meta_info.xml File.

8. Save and close the od_meta_info.xml file.

   The following code is an example of a complete object definition for Custom Object 1 in the od_meta_info.xml file:

   <SiebelMetaInfo>
   ...
   ...
       <object TypeId='Custom Object 1' Label='CustomObject1' LabelPlural='CustomObject1' ViewMode='Sales Rep' IntObjName='Custom Object 1' SiebMsgXmlElemName='CustomObject1' SiebMsgXmlCollectionElemName='ListOfCustomObject1'>
         <field Name='CreatedBy' Label='CreatedBy' DataType='DTYPE_TEXT'        IsHidden="yes"/>
         <field Name='CreatedById' Label='CreatedById' DataType='DTYPE_ID'        IsRefObjId="yes" RefObjTypeId="User" IsHidden="yes"/>
         <field Name='CreatedDate' Label='CreatedDate' DataType='DTYPE_UTCDATETIME'        IsHidden="yes"/>
          <field Name='Id' Label='Id' DataType='DTYPE_ID' IsPrimaryKey='yes' />
          <field Name='Name' Label='Name' DataType='DTYPE_TEXT' />
          <field Name='Description' Label='Description' DataType='DTYPE_TEXT' />
       </object>
   </SiebelMetaInfo>

Related Topics

Values for the Threshold Attribute of the Synchronizer Element

XML Code for Meta Information