Per Nergård (MVP)
+2
Sep 14, 2012
visibility 4889
star star star star star
(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.

http://yoursite.com/youreditpath/edit/XFormEdit.aspx?pageId=&parentId=&formid=fa8e1d3e-796c-426b-931a-a62bf51b9563&selectedFormName=/

 

* 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

Comments

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: http://world.episerver.com/Blogs/Tobias-Nilsson/Dates/2010/11/XForm-reserved-names-for-input-fields/

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

Per Nergård (MVP)
Per Nergård (MVP) 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.

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |