2908607 - LegacyPicklistID in MDF Picklist - Platform

'LegacyPicklistID' based validations added in MDF Picklist Import/Sync/Edit, for migrated instances.

Instances migrated to MDF picklists will have a required field LegacyPicklistID added to exported CSV file and also the picklist import template, with validations specific to the field. Purpose of this is to prevent the legacy picklist IDs from being overwritten during import, which can break the references to the migrated picklist

How to maintain LegacyPicklistID

• When you update an MDF picklist that was migrated from a legacy picklist, you should enter the corresponding LegacyPicklistID in the required field.
• When you create a new MDF picklist, you should enter the same LegacyPicklistID value as the ID field.
  
  

Validations for LegacyPicklistID

Following validations have been added with regard to MDF Picklist Import/sync:

1. If import file doesn't contain LegacyPicklistId column or if the column is empty, whole import should fail
2. If same picklist (MDF external code) has different LegacyPicklistId in source file, MDF import/validation (full-purge and incremental) should fail for specified rows
3. If different picklist (MDF external code) have same LegacyPicklistId in import file, import/validation should fail for specified rows
4. If the same picklist (MDF external code) on source and target have different LegacyPicklistIds, MDF import/validation (full-purge and incremental) should fail for specified rows

Following validations have been added with regard to MDF Picklist Edit in Picklist Center:

1. If the LegacyPicklistId being entered matches the value assigned to another MDF Picklist, error will be shown.
   
   

2714036 - How to Import and Export a MDF Picklist

LegacyPicklistID,MDF Picklist,Picklist Import , KBA , LOD-SF-MDF-PKL , Picklists , How To