Take the community feedback survey now.

Anders Hattestad
Mar 7, 2011
  3451
(1 votes)

Dynamic Properties with versioning V0.9

One thing I miss a lot is version on dynamic properties. I have been looking for clean solutions to add that to EPiServer, an think I have come up with an concept that can work, while we wait for CMS 7.

I have borrowed some code from Itera.Objects, that can display other properties inside one property. and used that together with Page Objects.

The concept is simple, I have one property that have all the dynamic properties inside it. When I save the page, I also save the dynamic properties inside the Page Object store. If the property is set to inherit, I delete the value from the store on this page. But my get value method checks all the stores up to the top to find the value.

image

As you can see from this picture the value for Writer is retrieved from page id 7 in en.

The pointers here is that we have to make the owner property be modified when a dynamic property is changed. This is because we need to trigger the save event. I also save the values after the page is saved, so the version is correct.

When I need to retrieve the dynamic property value I have made my own property handle. That load the values based on the page.

Hade a lot more of code in this blog post, but Live writer died, and I didn’t have any backup :(, but the core saving is done by creating a class that have the value for the property. This is because its a bit tricky to save a property data object to the store.

Code Snippet
  1. static void Instance_SavedPage(object sender, EPiServer.PageEventArgs e)
  2. {
  3.     foreach (var prop in e.Page.Property)
  4.     {
  5.         if (prop is PropertyDynamicProperties)
  6.         {
  7.             PageObjectManager pom = new PageObjectManager(e.Page);
  8.             foreach (var dynProp in (prop as PropertyDynamicProperties).AllDynamicProperties)
  9.             {
  10.                 if (dynProp.InheritValue)
  11.                 {
  12.                     pom.Delete(dynProp.Name);
  13.                 }
  14.                 else
  15.                 {
  16.                     if (dynProp.Property.IsNull)
  17.                         pom.Delete(dynProp.Name);
  18.                     else
  19.                     {
  20.                         if (dynProp.Property.IsLanguageSpecific)
  21.                             pom.Save(dynProp.Name, DynProperyStoreValue.GetObjectFromProperty(dynProp.Property, e.Page.Property), PageObject.OwnerOption.PageLanguageBranch);
  22.                         else
  23.                             pom.Save(dynProp.Name, DynProperyStoreValue.GetObjectFromProperty(dynProp.Property, e.Page.Property), PageObject.OwnerOption.PageVersion);
  24.                     }
  25.                 }
  26.                 }
  27.             }
  28.         }
  29.     }
  30. }

So i do it like this. As you can see I use the different methods of storing into the Page Object store depending on the dynamic property is unique pr languages or not.

The full code can be found in the code section.

What you need to do is to create a property of type DynamicProperties on each page type, and you are good to go.

Mar 07, 2011

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Introducing the beta of Opti Graph Extensions add-on

Introducing Opti Graph Extensions: Enhanced Search Management for Optimizely CMS I am excited to announce the beta release of **Opti Graph...

Graham Carr | Sep 15, 2025

Content modeling for beginners

  Introduction Learning by Doing – Optimizely Build Series  is a YouTube series where I am building  a fictional  website called  TasteTrail , food...

Ratish | Sep 14, 2025 |

A day in the life of an Optimizely OMVP - Enhancing Search Relevance with Optimizely Graph: Synonyms and Pinned Results

When building search experiences for modern digital platforms, relevance is everything. Users expect search to understand their intent, even when...

Graham Carr | Sep 14, 2025

Optimizely CMS and HTML validation message: Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

When using the W3C Markup Validation Service, some annoying information messages pop up because Optimizely CMS adds the trailing slash to...

Tomas Hensrud Gulla | Sep 14, 2025 |