Data model
Work with the data model and Entity Framework ORM
Optimizely uses Entity Framework for Configured Commerce. The following topics help you acclimate to the new data layer Goals and best practices Basic usage Extensibility Performance The goals of the Configured Commerce data layer are Use the Entity Framework.
Transactions and the unit of work
A UnitOfWork represents a single session against the database. You make changes through repositories, then persist them by calling Save (or SaveAsync ).
Entity extension considerations
Configured Commerce is designed to be highly configurable and extensible to accommodate a multitude of business needs. For example, an SAP ERP implementation stores customer data which includes organizational code.
Database objects to user interface label mapping
The Application Dictionary is designed to allow Implementors the capability of changing labels throughout the Admin Console. In doing this, some entities have both an ID (GUID) and an Object.
Custom properties
The Application Dictionary, housed within the Admin Console, manages entities that control such data as field names, field labels, language options, field length, and site security. Entities are outlines of objects in the Admin Console with various Custom Properties assigned to them.
Create a custom property in the application dictionary
The Application Dictionary is designed to be highly configurable to accommodate a multitude of business needs. Custom Properties are attributes attached to entities that can be created without custom development.
Create custom settings
Configured Commerce provides many standard settings that allow you to configure how the application behaves. These settings can be configured in the Admin Console.
Create custom tables with an entity and WebApi
Part of the implementation of custom tables support is to change the data model so that the IIS-connected user will no longer be able to execute SQL DDL statements directly. When this feature is implemented, three separate connection strings must be included in the connectionStrings.
Move content from pilot/sandbox to production
When a customer is working on a new site, they are generally creating and modifying their content in the pilot/sandbox environment until they are ready to go live. During that process, it is common to want to move the content from one site to another.
Use custom properties
The process of adding custom properties to an existing entity is covered in Create a custom property in the application dictionary. https //world.