Try our conversational search powered by Generative AI!

Per Nergård
Sep 14, 2012
(1 votes)

CMS5 to CMS6 upgrade. XForm validation

When upgrading a customer site from CMS5 to 6 we got some errors regarding XForms.

We got errors reporting of forms containing fields with names longer than 75 characters as well as forms with fields having duplicate names.

I wasn’t completely surprised that we got errors since my experience of upgrades of forms hasn’t been the best.

If your site isn’t migrated from 4.X you shouldn’t get any of these errors because EPiServer has added a lot of validation regarding forms starting from CMS5.

To avoid having to run the upgrade several times and so I next time can do a check for XForm problems in advance I  did a small program that goes through all forms checking for the type of errors we got in this particular case.

The program just prints out a table with the following information

Form-GUID, Form-name,Type of error found, PageId, Key

The PageId column contains a id to a page that uses the current form (it only contains one pageid even if the form is used on more pages), the key column contains the name of the offending XForm field if the error is a duplicate field.

To use it just download the zip file and drop the .aspx and .cs in your sites root folder and browse to it. If you later want to validate a specific form you can to by adding ?guid= to the url.

If you get many forms that aren’t used on any page it can be a bit of a pain locating them through the XForm UI, at least if you have a lot of forms. But there is a quick shortcut if you have the GUID.

Just add your site name, edit ui path and the GUID to the Url below and you will get straight into editing of the form.


* Update *

Added Henrik Stabergs suggestion to check for fields with id aswell. Wasn’t able to update the code section so the updated files can be downloaded from here


Sep 14, 2012


Sep 26, 2012 09:06 AM

Hi Per,
Thanks for a nice tool to validate xForms before upgrading!

I also got errors when upgrading xForms with input fields namned "id", "Id" och "ID".
More information in Tobias Nilssons article:

A check for this condition can easily be added to the method DoAllChecks(XForm xf) {...}

Sep 26, 2012 09:40 AM

Thanks for the input.

I've added the "id" check to the program but I have problem uploading it to the Code section.

Please login to comment.
Latest blogs
Fix your Search & Navigation (Find) indexing job, please

Once upon a time, a colleague asked me to look into a customer database with weird spikes in database log usage. (You might start to wonder why I a...

Quan Mai | Apr 17, 2024 | Syndicated blog

The A/A Test: What You Need to Know

Sure, we all know what an A/B test can do. But what is an A/A test? How is it different? With an A/B test, we know that we can take a webpage (our...

Lindsey Rogers | Apr 15, 2024

.Net Core Timezone ID's Windows vs Linux

Hey all, First post here and I would like to talk about Timezone ID's and How Windows and Linux systems use different IDs. We currently run a .NET...

sheider | Apr 15, 2024

What's new in Language Manager 5.3.0

In Language Manager (LM) version 5.2.0, we added an option in appsettings.json called TranslateOrCopyContentAreaChildrenBlockForTypes . It does...

Quoc Anh Nguyen | Apr 15, 2024