Concrete Field Migration Examples
These examples provide a practical "old field intent -> new field setup" path you can copy directly.
General Link [DAM] -> Plugin SingleSelect
Use when authors select one linkable Bynder asset.
Target setup on __Standard Values:
{"mode":"SingleSelect"}Optional document-focused setup:
{"mode":"SingleSelect","assetTypes":["document"]}Image [DAM, Single asset] -> Plugin SingleSelect + image filter
Use when one image is selected and rendering chooses derivative behavior in code.
Target setup on __Standard Values:
{"mode":"SingleSelect","assetTypes":["image"]}Image [DAM, Multi asset] -> Plugin MultiSelect
Use when one field should contain multiple selected assets.
Target setup on __Standard Values:
{"mode":"MultiSelect","assetTypes":["image"]}If mixed media is allowed, remove assetTypes.
Image [DAM, Single file] -> Plugin SingleSelectFile
Use when single-file behavior and author flexibility are required.
Target setup on __Standard Values:
{"mode":"SingleSelectFile"}Video [DAM] -> Plugin SingleSelect + video filter
Use when a single video is required.
Target setup on __Standard Values:
{"mode":"SingleSelect","assetTypes":["video"]}File [DAM] -> Plugin SingleSelectFile or SingleSelect
Use SingleSelectFile for file-oriented workflows, or SingleSelect for generic single asset selection.
Target setup on __Standard Values (file-oriented):
{"mode":"SingleSelectFile"}Target setup on __Standard Values (document-oriented):
{"mode":"SingleSelect","assetTypes":["document"]}