Siebel CRM Desktop for IBM Notes Administration Guide > Customizing Picklists > Process of Creating Hierarchical Picklists >

Modifying the Basic Mapping and Forms to Support Hierarchical Picklists


This task is a step in Process of Creating Hierarchical Picklists.

In this topic you modify the basic mapping and forms to support a hierarchical picklist.

To modify the basic mapping and forms to support a hierarchical picklist

  1. Add the parent field to the basic mapping. Do Adding Fields to the Basic Mapping to Support Static Picklists, but use the following code:

    <field id="JVD Hier Parent">
      <reader>
        <lotus_std>
          <lotus_field id="JVDHierParent" />
            <convertor>
              <string />
            </convertor>
        </lotus_std>
      </reader>
      <writer>
        <lotus_std>
          <lotus_field id="JVDHierParent" />
            <convertor>
              <string />
            </convertor>
        </lotus_std>
      </writer>
    </field>

  2. Add the child field to the basic mapping. Do Adding Fields to the Basic Mapping to Support Static Picklists, but use the following code:

    <field id="JVD Hier Child">
      <reader>
        <lotus_std>
          <lotus_field id="JVDHierChild" />
            <convertor>
              <string />
            </convertor>
        </lotus_std>
      </reader>
      <writer>
        <lotus_std>
          <lotus_field id="JVDHierChild" />
            <convertor>
              <string />
            </convertor>
        </lotus_std>
      </writer>
    </field>

  3. Create the type that stores the list of values for the parent picklist. Do Modifying the Basic Mapping to Store Values for Static Picklists, but use the following code:

    <type id="OpportunityJVD Hier ParentPicklist">

    Bold text identifies the code that is different for a hierarchical picklist. For more information about doing this step, see Step 4.

  4. Create the type that stores the list of values for the child picklist. Do Modifying the Basic Mapping to Store Values for Static Picklists, but use the following code:

    <type id="OpportunityJVD Hier ChildPicklist"
    predefined_folder="1" ver="1">
    <form message_class="IPM.Contact.SBL.OpportunityJVD_Hier_ChildPicklist"></form>

    Bold text identifies the code that is different for a hierarchical picklist. For more information about doing this step, see Step 4.

  5. Allow the child picklist to store the value from the parent field. You add the following code to the OpportunityJVD Hier ChildPicklist type that you created in Step 4:

    <field id="Parent">
      <reader>
        <lotus_std>
          <lotus_field id="Parent" />|
            <convertor>
              <string />
            </convertor>
        </lotus_std>
      </reader>
    <writer>
      <lotus_std>
        <lotus_field id="Parent" />
          <convertor>
            <string />
          </convertor>
        </lotus_std>
      </writer>
    </field>

  6. Open IBM Domino Designer, and then open the following form:

    (SBL)form:opportunity

    For more information, see Opening IBM Domino Designer.

  7. Create the JVD Hier Parent combobox.
  8. Create the JVD Hier Child combobox.
Siebel CRM Desktop for IBM Notes Administration Guide Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.