A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Per Nergård (MVP)
Sep 14, 2012
  4542
(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.

Please login to comment.
Latest blogs
From 12 to 13 preview: A Developer's Guide to testing an Optimizely CMS 13 Alloy Site

The release of Optimizely CMS 13 marks a significant step forward, embracing a more composable and headless-first architecture. While this unlocks...

Robert Svallin | Jan 23, 2026

A day in the life of an Optimizely OMVP: Opti North Manchester - January 2026 Meetup Recap

There's something special about the Optimizely community in the North. On 22nd January, we gathered at the Everyman Cinema in Manchester for the...

Graham Carr | Jan 23, 2026

Beyond the widget - making Optimizely Content Recommendations work for you

Optimizely recommendation data you can render your way. A frontend-focused guide to bypassing the widget, with practical query filtering advise and...

Tom Robinson | Jan 22, 2026 |

Announcing the Jhoose Commerce API for Optimizely Commerce Connect

A layered framework for Optimizely Commerce Connect that accelerates delivery, supports headless architecture, and simplifies carts, checkout, and...

Andrew Markham | Jan 22, 2026 |