Oracle CRM On Demand Desktop Customization Guide > Adding Custom Fields to Oracle CRM On Demand Desktop > Adding Custom Fields to Oracle CRM On Demand Desktop >

Changing the XML Code in the od_basic_mapping.xml File


The od_basic_mapping.xml file provides the data mapping between Oracle CRM On Demand and Oracle CRM On Demand Desktop. In this procedure, you add the Membership field mapping to the object <type> element.

If you are adding a field to the object stored in DB FACADE storage in Oracle CRM On Demand Desktop, then the syntax for adding the <field> element is as follows:

<field id ="Membership">
<type>
<simple type="string"/>
</type>
</field>

For more information on DB FACADE storage, see About Microsoft Outlook and DB FACADE Storage.

To change the XML Code in the od_basic_mapping.xml file

  1. In the od_basic_mapping.xml file, locate the Contact <type > element, which looks similar to the following:

    <type id="Contact"...>

  2. Add the following <field> mapping element after any existing <field> mapping elements:

    <field id="stMembership">
    <reader>
    <mapi_user>
    <user_field id="od Membership" ol_field_type="1"></user_field>
    <convertor><string/></convertor>
    </mapi_user>
    </reader>
    <writer>
    <outlook_user>
    <user_field id="od Membership" ol_field_type="1"></user_field>
    <convertor> <string/></convertor>
    </outlook_user>
    </writer>
    </field>

    A field map has a reader and a writer definition for a custom field as shown in this example. You choose your own name for the custom field, and you must use the right converter for converting the field type. For example, to convert an incoming value of integer type to string, you must use the following structure:

    <converter>
    <string/>
    </converter>

    The following XML code shows the Contact <type> element and the <field> mapping element highlighted in bold font:

    <type id="Contact" predefined_folder="10" ver="7">
    <form message_class="IPM.Contact.OnDemand.Contact" icon="type_image:Contact:16" large_icon="type_image:Contact:32" display_name="#obj_contact">OnDemand Contact</form>
    <alt_messageclasses>
    <alt_messageclass ext="Private" display_name="#obj_private_contact" icon="type_image:Contact.Private:16" large_icon="type_image:Contact.Private:32">OnDemand Contact</alt_messageclass>
    </alt_messageclasses>
    <upgrade>
    <from message_class="IPM.Contact" target_message_class="IPM.Contact.OnDemand.Contact.Private"></from>
    </upgrade>
    <custom_views default_name="#view_crm_and_personal_contacts">
    <view id="all_contacts" name="#view_crm_and_personal_contacts"></view>
    </custom_views>
    <field id="CellularPhone">
    <reader>
    <mapi_std>
    <mapi_tag id="0x3A1C0000"></mapi_tag>
    <convertor>
    <string/>
    </convertor>
    </mapi_std>
    </reader>
    <writer>
    <outlook_std>
    <outlook_field id="MobileTelephoneNumber"></outlook_field>
    <convertor>
    <string/>
    </convertor>
    </outlook_std>
    </writer>
    </field>

    <field id="stMembership">
    <reader>
    <mapi_user>
    <user_field id="od Membership" ol_field_type="1"></user_field>
    <convertor><string/></convertor>
    </mapi_user>
    </reader>
    <writer>
    <outlook_user>
    <user_field id="od Membership" ol_field_type="1"></user_field>
    <convertor> <string/></convertor>
    </outlook_user>
    </writer>
    </field>
    ...
    ...
    </type>

  3. Verify your changes, and save the forms_12.xml file.
Oracle CRM On Demand Desktop Customization Guide, Version 5.2 Revision A Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.