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
  10690
(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
Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025

Optimizely PaaS Administrator Certification : Free for Everyone

Optimizely has recently launched a free PaaS Administrator Certification. https://academy.optimizely.com/student/activity/2958208-paas-cms-administ...

Madhu | Dec 9, 2025 |

Fixing TinyMCE Initialization Failures in Optimizely CMS: A Hidden Pipeline Issue with .NET SDK Versions

Over the past few weeks, several Optimizely CMS projects began experiencing a puzzling failure: XHtmlString fields stopped initializing TinyMCE in...

Francisco Quintanilla | Dec 9, 2025 |

Jhoose Security Modules v2.6.0 — Added support for Permissions Policy and .NET 10

Version 2.6.0 adds Permissions Policy header support, updates to .NET 10, improved policy management, configurable security settings, and enhanced...

Andrew Markham | Dec 6, 2025 |