Try our conversational search powered by Generative AI!

Stefan Forsberg
May 7, 2009
(0 votes)

Page Provider – Part three

Mapping your data to properties on the episerverpage is a fairly simple process. In the GetLocalPage method we simple use the SetValue on our created PageData object.

The standard page has two properties called MainBody and  SecondaryBody so let’s set some values on those properties.

protected override EPiServer.Core.PageData GetLocalPage(EPiServer.Core.PageReference pageLink, EPiServer.Core.ILanguageSelector languageSelector)
    PageData pageData = new PageData();
    Development.DataAbstraction.SimplePage activeSimplePage = GetSimplePage(pageLink);
    // Finds the parent to our page.
    PageReference parentLink = (pageLink.ID == parentPage.ID) ? base.EntryPoint : base.ConstructPageReference(parentPage.ID);
        new List<string>() {}
    pageData.SetValue("MainBody", "Some text");
    pageData.SetValue("SecondaryBody", "Some other text");
    return pageData;


This works well for simple string based properties  (both MainBody and SecondaryBody are of type xhtml string). So let’s try to work with a more complex property type, for instance the link collection. To do this we start with adding a property of that type called Links to our standard page page type.

To get a feel for how this works let’s start with just setting the property to some string value and see what happens.

   1: pageData.SetValue("Links", "Link1");

This leads to the exception System.ArgumentException: Passed object must be of type LinkItemCollection. So apparently we need to create a LinkItemCollection and map it to the property data.

EPiServer.SpecializedProperties.LinkItemCollection links = new EPiServer.SpecializedProperties.LinkItemCollection();
EPiServer.SpecializedProperties.LinkItem linkItem = new EPiServer.SpecializedProperties.LinkItem();
linkItem.Href = "";
linkItem.Text = "Aftonbladet";
linkItem = new EPiServer.SpecializedProperties.LinkItem();
linkItem.Href = "";
linkItem.Text = "IDG";
pageData.SetValue("Links", links);


This is a somewhat unlikely scenario (to create the links programmatically that is). A more likely task is that the customer wants to add additional info to their data. Say for instance that the customer wants to add some links to their products that they for some reason don’t want or are unable to store in their product database.

What we’d do then is to give the page provider the capabilities to edit the page and when the user saves the page we save the property value of the link collection to some repository and then build logic to fetch the same data on the loading of the page (GetLocalPage).

This is what we’ll explore in the next post.

May 07, 2009


Please login to comment.
Latest blogs
Roll Your Own Security Headers

Proper security headers are a must for your Optimizely driven website. There are a variety of tools out there that will help with this, but when...

Ethan Schofer | Feb 21, 2024

Migrate Catalog content properties

A colleague asked me yesterday – how do we migrate properties of catalog content. There is, unfortunately, no official way to do it. There are...

Quan Mai | Feb 20, 2024 | Syndicated blog

Adjust log levels in Optimizely DXP

You may adjust the log levels for your site in Optimizely DXP yourself, but only for the Integration environment. Follow this step-by-step guide.

Tomas Hensrud Gulla | Feb 20, 2024 | Syndicated blog

Introducing Search & Navigation Dashboard for Resource Usage

We're excited to unveil the latest addition to the Search & Navigation suite: a dashboard designed to proactively monitor your resource usage. It's...

Edvin Dackelid Johansson | Feb 20, 2024