2088678 - Legacy Picklists: How to Setup Cascading Picklists - Platform

SAP Knowledge Base Article - Public

2088678 - Legacy Picklists: How to Setup Cascading Picklists - Platform

Symptom

  • This KBA focuses only on Legacy picklists. For MDF picklists see KBA 2328179 - Legacy to MDF Picklist Migrations | General Information

  • How to Setup Cascading Picklists.
     
  • Cascading picklists allow long lists of values to be reduced to a more manageable size by linking values to a parent value in another field. Once the parent value is selected, the system will immediately populate the child dropdown menu with the corresponding options. Users will not be able to pick a value in the "child" picklist before a value in the "parent" picklist is selected.

Environment

  • BizX Platform
  • SAP Success Factors Recruiting Management 

Resolution

Cascading Picklists

    As of b0811, cascading picklists are supported on these application pages:

  1. Ultra employee profile
  2. Succession Talent Search
  3. All relevant Recruiting pages, including: 
  1. Job Requisition (JRDM)
  2. Candidate Profile (CPT)
  3. Job Application (CDM)
  4. Advanced Candidate Search Criteria    

     The v10 live profile page does not support cascading picklists.

  • Cascading picklists allow long lists of values to be reduced to a more manageable size by linking values to a parent value in another field. Once the parent value is selected, the system will immediately populate the child dropdown menu with the corresponding options. Users will not be able to pick a value in the "child" picklist before a value in the "parent" picklist is selected.
     
  • If a child field already had a value that is rendered invalid by a change to the parent field selection, the child field value will revert to the blank option at the top of the drop-down menu, to avoid saving bad data.
     
  • To set up the relationships between values, the import file now optionally includes a column called "parentOptionId", where you can enter the OptionId of the "parent" picklist value that must be selected for the "child" picklist option to appear.
     
    For example, in the list below, the value "Aberdeen Univ" is dependent on picklist OptionId 1965 (United Kingdom), while "Arizona State Univ" is dependent on picklist OptionId 1966 (United States):
     
  • A new child picklist must be imported separately from (and after) the parent picklist, so that you can populate the parentOptionId field with the parent IDs.
     
  • Picklist items can still have a blank parentOptionId. These items will always appear regardless of other selections (the default behavior).
     
  • The picklist export function always includes this column, even if you didn't include it on your original import.
     
  • The picklist import function guards against some common configuration errors, including:
  1. An item referencing a parentOptionId whose parentOptionId is the original item (direct circular reference)
  2. An item referencing a parentOptionId that is in the same picklist (invalid dependency).

When configuring picklists on your data entry layouts, parent picklists must precede child picklists on the page, and should generally be in the same section (portlet). For example, you cannot have a "country" picklist drive a "zip code" picklist that appears above it on the screen.

Note: In Recruiting, there is a specific cascading picklist that does NOT use the picklist infrastructure. These are the "country" and "stateProvince" fields on the JRDM. These fields are defined as "enum"s as their type. They are special because these values map to specific tokens that are used for the eQuest configuration. They do follow the same recommended ordering as cascading picklists, however. Please always define "country" before defining "stateProvince" on a JRDM.

Data Model Configuration

  • Note: this section describes back-end instance configuration options that must be performed by Professional Services or the Customer Success team.
  • Picklists cannot be used for user directory fields (those fields set in the standard user import file); they can only be used for elements populated through a personal or background data import file. They cannot be used on numeric or date fields.
     
  • For cascading picklists, the <picklist> tag includes an attribute to specify a field from which the system should check for a parent field value. This can be set up in two places:
  1. Among standard-element definitions, where one standard element's picklist values are always dependent on another's.
  • A single parent field could drive the options in more than one child picklist. For example, the riskOfLoss field value could drive the picklist options for both impactOfLoss and another field, such as reasonForLeaving.
  1. Within a background-element section, specifying another field within that same background-element.
  • Both field types use the same reference syntax in the picklist field:
     
  • The live profile data model import mechanism does not validate the parent-field-id value, so take extra care to ensure you are specifying a valid field ID.
     
  • The parent and child picklist fields should use the same read and write permissions. Otherwise you may get in a situation where a user can edit a child ID and not a parent ID, or vice versa, which can cause errors.
     
  • A field that is the parent to another dependent field can also itself be dependent on another parent. In other words, there can be multiple levels of cascade. For example:

    1. Select "Region" à reset "Country" drop-down list to valid options

    2. Select "Country" à reset "School" drop-down list to valid options

    3. Select "School"

  • The Recruiting module configuration follows the same pattern as the data model configuration. For example, the candidate profile and application data models both use the picklist parent-field-id just like the live profile data model.
     
  • To use cascading picklists for recruiting data model fields, the live profile data model must also use the same cascading picklist configuration for the linked fields.
     
  • Unlike the live profile data model import, the recruiting candidate data model import mechanism does validate the parent-field-id to ensure that it (1) exists, (2) is not a self-reference, and (3) uses a picklist.

Keywords

 child picklist read only , KBA , sf picklist , LOD-SF-PLT , Foundational Capabilities & Tools , LOD-SF-PLT-PCK , Picklist Management Issue , LOD-SF-RCM-JOB , Job Postings & Requisitions , How To

Product

SAP SuccessFactors HCM Core all versions ; SAP SuccessFactors Recruiting all versions