Last updated: Oct 24 2016

Area: Episerver Commerce Applies to versions: 10 and higher
Other versions:

Assets and media

This topic introduces asset and media management in Episerver Commerce. The asset management system supports generic, content-based files, which are used by Episerver products such as CMS and Commerce. Assets, such as blocks and media files in CMS, are accessible via the Assets pane of the Edit user interface and the product catalog in Commerce. Media files are images, videos, and documents.

See the Content  section of the Episerver CMS Developer Guide for information about the Episerver platform content model and asset management. This topic describes the Commerce-specific parts of the assets management integration.

Note: Entry-associated assets, which correspond to the For this page folder in CMS, are not available for Commerce. You can only work with shared assets for Commerce content.

Asset management in Commerce

The content-based asset management system with the BLOB provider model adds assets to the catalog nodes and entries when you manage catalogs. Files are stored in the same location as the Episerver CMS files, providing a unified user experience.

In a Commerce installation, you can access products and product variants from the product catalog via the Catalogs gadget in the Assets pane, with support for drag and drop of content items into CMS pages and blocks. The integration is done using content type classes EPiServer.Commerce.Catalog, EPiServer.Commerce.Catalog.ContentTypes and EPiServer.Commerce.Catalog.Provider. 

Default asset for content

EntryContentBase and NodeContent implements IAssetContainer, which contains the property CommerceMediaCollection. Content that implements the IAssetContainer interface can contain several assets. In many cases, only one of the assets is shown at the site. The first item in the asset collection list is used in the UI by default. See also Asset URL resolver.

Related topics

Comments