2815327 - MDF import template header is confusing

The Department Foundation Object import template and some fields are related to picklist. The field's second headers are "Picklist Value.External Code". What is the meaning of such headers it's confusing.

SuccessFactors

Employee Central v2

Metadata Framework

Foundation Objects

• Go to Department Object Definition (or any other custom or Foundation object definition)
• Add a custom string field and associate it with a picklist.

• Save object definition.
• Export Department object template from "Import and Export Data".

• Open the template and observe second header row for the custom picklist field that you have created, it will appear as "Picklist Value.External Code".

First header row of import file will show the field IDs stored in database

Second head row of import file will show either the Label which we have provided or a hint. For example: "Picklist Value.External Code" if it's of picklist type.

"Picklist Value.External Code" is a hint which indicates to use associated field's picklist's externalCode in import file instead of picklist values.

Workaround Only Applicable for Foundation Objects

Use "Import Foundation Data" tool to export Department Template.

Here the label of the custom picklist filed shows instead of the hint "Picklist Value.External Code"

"Picklist Value.External Code", import template headers, foundation object import template, generic object import template, SuccessFactors , KBA , foundation object import template , picklist value.external code , successfactors , LOD-SF-EC-FOO , Foundation Objects (Organisation, Pay and Job Structures) , LOD-SF-MDF , Metadata Framework , Problem