Field Type Mapping (XP/XM -> SitecoreAI)
Use this as your primary template migration reference.
Core Model Change
In XP/XM, teams commonly used multiple DAM-specific field types such as:
- General Link [DAM]
- Image [DAM, Single asset]
- Image [DAM, Multi asset]
- Image [DAM, Single file]
- Video [DAM]
- File [DAM]
In SitecoreAI, migration targets one connector field type:
- Field type: Plugin
- Source value:
pub-acdcf8ff-54f9-4269-977a-c4be5b8fde10 - Source meaning: Bynder DAM Connector for SitecoreAI public Marketplace App ID
- Configuration location: Field value (typically on
__Standard Values) - Configuration parameters: optional
mode(defaults toSingleSelectFile), optionalassetTypes, optionaldefaultSearchTerm, optionalhideLimitedUse, and future parameters - Full parameter reference: Plugin Field Options
Mapping Table
| XP/XM field type | SitecoreAI field type | Mode | Asset types |
|---|---|---|---|
| General Link [DAM] | Plugin (bd_BynderBaseSingleSelect) | SingleSelect | all or ['document'] |
| Image [DAM, Single asset] | Plugin (bd_BynderBaseImage) | SingleSelect | ['image'] |
| Image [DAM, Multi asset] | Plugin (bd_BynderBaseMultiSelect) | MultiSelect | all or ['image'] |
| Image [DAM, Single file] | Plugin (bd_BynderBaseSingleFile) | SingleSelectFile | all |
| Video [DAM] | Plugin (bd_BynderBaseVideo) | SingleSelect | ['video'] |
| File [DAM] | Plugin (bd_BynderBaseSingleFile / bd_BynderBaseSingleSelect) | SingleSelectFile or SingleSelect | all or ['document'] |
Notes:
- Prefer pre-delivered base templates for faster migrations.
- Use custom Plugin fields when exact legacy field naming must be preserved.
- Set
assetTypesexplicitly when strict media filtering is required.