SitecoreAI Connector
Setup & Configuration
Custom Field Types

Custom Field Types

Set up the Bynder field in Sitecore templates before content authors can select assets.

This is a developer/admin setup task (template modeling), not an authoring task.

Option 1: Use a Pre-Delivered Base Template

The recommended approach for most use cases:

Pre-Delivered Base Templates

The connector includes seven pre-built base templates under /sitecore/templates/Modules/BynderDam. Choose the one that matches your asset selection requirements:

TemplateField NameModeAsset TypesUse Case
bd_BynderBaseSingleFileBynderDamSingleFileSingleSelectFileAllSingle file selection with DAT support
bd_BynderBaseSingleSelectBynderDamSingleSelectSingleSelectAllSingle asset selection
bd_BynderBaseMultiSelectBynderDamMultiSelectMultiSelectAllMultiple asset selection
bd_BynderBaseImageBynderDamImageSingleSelectimageImage-only selection
bd_BynderBaseVideoBynderDamVideoSingleSelectvideoVideo-only selection
bd_BynderBaseAudioBynderDamAudioSingleSelectaudioAudio-only selection
bd_BynderBaseDocumentBynderDamDocumentSingleSelectdocumentDocument-only selection

All fields are configured as Plugin type with source ID: pub-acdcf8ff-54f9-4269-977a-c4be5b8fde10 (Bynder DAM Connector for SitecoreAI public Marketplace App ID)

For full template details, see What Gets Created.

  1. When creating a new template or content item, base it on one of the seven base templates above
  2. The Bynder field is automatically available with the correct mode and asset types configured
  3. Content authors can now select assets in the Bynder selector filtered to the appropriate type

Option 2: Add a Custom Plugin Field

To add the Bynder asset selector to an existing page or component template:

  1. Open your template in the Content Editor
  2. Add a new field of type Plugin
  3. In the Source field, enter: pub-acdcf8ff-54f9-4269-977a-c4be5b8fde10 (Bynder DAM Connector for SitecoreAI public Marketplace App ID)
  4. Save the template
  5. The Bynder asset picker is now available for that field
  6. (Optional) Configure field options on the field's __Standard Values (see Plugin Field Options for details)

Next Steps