Template Modeling for Mixed Sitecore + Bynder Scenarios
If authors must be able to choose from both Sitecore media and Bynder, model this explicitly with two fields.
Recommended pattern:
- One native Sitecore field (for example Image or File field)
- One Bynder Plugin field with the required mode/assetTypes
Do not force both source types into one field model. Keeping fields explicit makes authoring and rendering rules clearer and easier to validate.
Example migration modeling decision
- Legacy single DAM image field -> two target fields:
HeroImageSitecore(native Sitecore Image)HeroImageBynder(Plugin with{"mode":"SingleSelect","assetTypes":["image"]})
Then define render precedence in code (for example: Bynder first, fallback to Sitecore, or vice versa).