A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

smithsson68@gmail.com
Dec 22, 2009
  10714
(1 votes)

Dynamic Data Store Feature List in EPiServer CMS 6 Release Candidate

The EPiServer CMS 6 Release Candidate is quite near now so I wanted to list the features in the Dynamic Data Store that have made it this far.

Saving Data

+ Save compile-time typed data (normal .NET classes)

+ Save runtime typed data (using EPiServer.Data.Dynamic.PropertyBag class)

Loading Data

+ Load data as the Type is was saved as

+ Load data into a PropertyBag

+ Load data into a different .NET Type to the one that was saved

Finding & Searching Data

+ Simple Find using equality matching for one or more properties

+ LINQ support for more advances scenarios

POCO Support

+ Internally managed identity for object graph support

+ Stateful store instances for CRUD operations

+ Ability to provide identity separate from object when saving

Type to Store Mapping

+ Globally using EPiServer.Data.Dynamic.GlobalTypeToStoreMap

+ Globally using EPiServer.Data.Dynamic.EPiServerDataStoreAttribute

+ Locally using EPiServer.Data.Dynamic.TypeToStoreMapper delegate

Store to Custom Big Table Mapping

+ Using EPiServer.Data.Dynamic.StoreDefinitionParameters

+ Using EPiServer.Data.Dynamic.EPiServerDataTableAttribute and EPiServer.Data.Dynamic.EPiServerDataColumnAttribute

Indexing of Properties

+ Using EPiServer.Data.Dynamic.StoreDefinitionParameters

+ Using EPiServer.Data.Dynamic.EPiServerDataIndexAttribute

Custom Mapping of .NET Type

+ Using System.Runtime.Serialization.DataContractAttribute and DataMemberAttribute

+ Using EPiServer.Data.Dynamic.EPiServerDataContractAttribute and EPiServerDataMemberAttribute

+ Using EPiServer.Data.Dynamic.ITypeHandler

Store Re-mapping

+ Add new properties

+ Remove properties

+ Rename properties

+ Change data type of properties (where convertible)

Type Resolving

+ Automatic .NET Type resolving (e.g. when an assembly gets a new version number)

+ Programmer controlled .NET Type resolving via Assembly redirects

 

I aim to provide some simple How To’s for all of the features over the coming days and weeks.

Dec 22, 2009

Comments

Sep 21, 2010 10:33 AM

The How To´s could be presented at Techforum in Norway 21th of January? We look forward to see and hear you!

Sep 21, 2010 10:33 AM

Indeed! Looking forward to it.
/ Paul Smith

Please login to comment.
Latest blogs
Looking back at Optimizely in 2025

Explore Optimizely's architectural shift in 2025, which removed coordination cost through a unified execution loop. Learn how agentic Opal AI and...

Andy Blyth | Dec 17, 2025 |

Cleaning Up Content Graph Webhooks in PaaS CMS: Scheduled Job

The Problem Bit of a niche issue, but we are building a headless solution where the presentation layer is hosted on Netlify, when in a regular...

Minesh Shah (Netcel) | Dec 17, 2025

A day in the life of an Optimizely OMVP - OptiGraphExtensions v2.0: Enhanced Search Control with Language Support and Synonym Slots

Supercharge your Optimizely Graph search experience with powerful new features for multilingual sites and fine-grained search tuning. As search...

Graham Carr | Dec 16, 2025

A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025