3150669 - A worksheet field's value becomes inconsistent when mapped to a picklist - Compensation Management

Usually a custom string field, mapped to an EC field which is referenced to a picklist with label translation. The field value appears inconsistent in the form or in Executive Review - some are showing in English, and there values that are translated to a different language other than the language used by the viewing user.

SuccessFactors Compensation Management

SuccessFactors Variable Pay

1. Create a  custom string field in EC and add picklist as Type of Reference Object and select the intended Picklist to use.

2. Import value on this field for your users

3. Add a custom string field in your Compensation plan/template and map to this custom string field you created in EC.

4. Launch your form and you will notice that some form member's is showing the value in English language while others were showing in different language.

The picklist value are translated to the form member's language.

The proper way of mapping a field to an EC field using a picklist is using by using its External Code.

Mapping should be i.e.

EC Category: Compensation Information

EC Field: Is Eligible.Code

In the template xml, code is a follows;

<comp-ect-input-field-map componentType="compInfo" fieldName="custom-string2.externalCode"/>

In this way, external_code in picklist will be used, then the value will be constant in any locale.

translated, translation, picklist, EC picklist, compensation mapping,  , KBA , LOD-SF-CMP-ADM , Admin Tools, Settings, Permissions , LOD-SF-CMP-EC , EC data, EC mappings, configuration & settings , Problem