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

Catalog DTO and Object models

Recommended reading 

Catalog entry DTOs and caching

Catalog entry DTOs transfer data between your application and the database. Catalog entry DTOs are cached based on your ecf.catalog.config settings. For example:

<?xml version="1.0"?>
<Catalog autoConfigure="true">
<Connection connectionStringName="EcfSqlConnection" />
<Cache enabled="true" collectionTimeout="0:1:0" entryTimeout="0:1:0" nodeTimeout="0:1:0" schemaTimeout="0:2:0" />

During development, it can be beneficial to disable caching. When deploying your e-commerce site, enable catalog caching, and use cache timeouts appropriate for your requirements and environment.

CatalogEntry DTOs are cached based on the response group(s) used to retrieve them. Types of CatalogEntry response groups:

  • Request
  • CatalogEntryInfo
  • CatalogEntryFull
  • Associations
  • Children
  • Assets
  • Nodes
  • Variants
  • Inventory
  • RecursiveAssociations

Catalog entry objects vs. catalog entry DTOs

Entry objects are used to further abstract catalog entry DTOs.

Entry objects are not cached, but the underlying DTOs from which they are constructed are cached.

Importing using API

Example: Using the Catalog API data transfer objects (DTOs) to create a catalog entry. The CatalogContext is the main entry point to the Catalog system.

Importing multiple language metadata

Example: Creating metadata in multiple languages for a catalog, using the MetaHelper.SetMetaFieldValue method.

Do you find this information helpful? Please log in to provide feedback.

Last updated: Nov 28, 2016

Recommended reading