- When importing picklist fields why is the picklists' label is used as the key?
- Why cannot the external-code be the key to the system?
- If picklist label must be the key, why is it possible to register duplicate labels when registering a master?
SAP SuccessFactors HXM Core
Imports engine was designed to use picklist labels from the inception of this feature. As a general request at that time was to provide a mechanism which is user input friendly, meaning many users wanted to use the text seen in the people profile and add it to the imports template.
With the evolution of the product we believe this request may be of interest now for other customers as well.
As such, we highly encourage you to please create a request on the influence tool with this request and based on the interest/votes we could definitely check the feasibility to support external code for picklist fields in our template and come up with the plan.
Continuous Influence is a great program for customers and partners to share feedback / ideas that help enhance SAP solutions in production. It enables customers to submit ideas and to vote on them.
Proposed Solution: Please create influence request for new design changes.
2824572 - Non-Unique External Code - MDF Picklist
2409842 - Error "is an invalid picklist value in import file or database for" When Importing File With Cascading Picklist Values.
2090228 - How to Submit Ideas for SAP SuccessFactors Products
external-code is unique in the Picklist configuration, picklists' label is used as the key for importing picklists , KBA , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , LOD-SF-PLT , Platform Foundational Capabilities , Product Enhancement