smithsson68@gmail.com
Oct 28, 2014
  5357
(4 votes)

DDS Remap Type Admin Plug-in

After reading this blog post I was inspired to make an EPiServer CMS Admin Plug-in to allow a Type remap in the DDS to be done direct from the site. This will come in useful when a Type you store in the DDS has changed and it is not decorated with the EPiServerDataStoreAttribute and / or the AutomaticallyRemapStore property is not set to true.

The plug-in is available here as an EPiServer Add-on. I will also make the source code available shortly.

NOTE: There seems to be a caching bug in the DDS code which means that the remap isn’t always effective until the site is restarted. The bug has been reported (unofficially confirmed as a bug) and will hopefully be fixed in due course.

Oct 28, 2014

Comments

Antti Alasvuo
Antti Alasvuo Oct 29, 2014 06:57 PM

Nice :) Have to give it a try next time when in the "bad" situation.

per
per Nov 14, 2014 04:58 PM

BAM -> http://world.episerver.com/Documentation/Release-Notes/ReleaseNote/?releaseNoteId=118973

smithsson68@gmail.com
smithsson68@gmail.com Nov 26, 2014 12:53 PM

Thanks Per!!

The source code can be found here -> http://bitbucket.org/smithsson68/ddstyperemapperaddon

Please login to comment.
Latest blogs
Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |