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

Anders Hattestad
Jan 12, 2011
  5700
(0 votes)

Dynamic Data Store and new properties on Types

When you use access the data store you get your object with the properties from the first time you created the store. If you have added properties on thje type the definition in the store is not updated, and your object will be missing values from the new properties.

That's a bit hassle, since I guess most of you will add new properties after the first time the store is created.

So instead of accessing the store like this

Code Snippet
  1. public static DynamicDataStore Store
  2. {
  3.     get
  4.     {
  5.         return DynamicDataStoreFactory.Instance.GetStore(typeof(ProductItem)) ??
  6.                DynamicDataStoreFactory.Instance.CreateStore(typeof(ProductItem));
  7.     }
  8. }
I have created myself and extension method so
Code Snippet
  1. public static DynamicDataStore Store
  2. {
  3.     get
  4.     {
  5.         return DynamicDataStoreFactory.Instance.GetCreateEnsureStore(typeof(ProductItem));
  6.     }
  7. }

Where the actually code is like this.

Code Snippet
  1. using System;
  2. using System.Collections.Generic;
  3. using System.Linq;
  4. using System.Web;
  5.  
  6. namespace EPiServer.Data.Dynamic
  7. {
  8.     public static class StoreExtensions
  9.     {
  10.         static object lockObject = new object();
  11.         static Dictionary<Type, bool> done = new Dictionary<Type, bool>();
  12.         public static DynamicDataStore GetCreateEnsureStore(this DynamicDataStoreFactory factory,Type type)
  13.         {
  14.             bool isFirstTime = true;
  15.             lock (lockObject)
  16.                 if (!done.TryGetValue(type, out isFirstTime))
  17.                     isFirstTime = true;
  18.             if (isFirstTime)
  19.             {
  20.                 var result= factory.GetStore(type);
  21.                 if (result == null)
  22.                     result = factory.CreateStore(type);
  23.                 else
  24.                 {
  25.                     var def = result.StoreDefinition;
  26.                     def.Remap(type);
  27.                     def.CommitChanges();
  28.                 }
  29.                 lock (lockObject)
  30.                 {
  31.                     done[type] = false;
  32.                 }
  33.                 
  34.             }
  35.             return factory.GetStore(type);
  36.         }
  37.  
  38.     }
  39. }

This code will on the first time it get accessed, checks if the store exits, and if not creates it. And if it exists, it will be remap to the type before it returns the store.

Jan 12, 2011

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026