smithsson68@gmail.com
Aug 18, 2010
visibility 9132
star star star star star
(2 votes)

EPiServer CMS XForm Search Gadget

In EPiServer CMS 6, XForms and their respective posts found a new home in the Dynamic Data Store (DDS). As the DDS has a Language Integrated Query (LINQ) enabled API, the opportunities for searching through XForm posts increased greatly.

With that in mind, I decided to develop a gadget with the target audience being site editors / owners / marketing guy, rather than developers.

Once the gadget has been installed using the EPiServer Deployment Center, it can be found in the EPiServer Online Center of the chosen site:

image

Once added to your dashboard, you select the XForm whose posts you want to search in:

image

Once the XForm has been selected, you are then presented with a search input panel to allow you to filter your search results:

image

The search can be filtered by all of the input fields on the XForm along with the post date and username of the poster.

You can then decide how to sort the output and which format you would like it in:

image

Once you’ve clicked the Search button, you should see the output either in the gadget or as a file download, depending on what format you chose:

image

The gadget can be configured using it’s menu in the top right hand corner:

image

The number of results per page as well as the CSV output value delimiter can be configured:

image

The default CSV output delimiter is a comma. Note that users whose Windows Region and Language settings are set to a locale that uses commas in numbers (such as Sweden) will need to set their CSV value delimiter to the appropriate value (semi-colon is used in most cases).

The EPiServer Deployment Center installation module for the gadget can be found here and the full source code here.

Developers are welcome to amend and customize the gadget as they see fit or just use it as is. It is currently localized to English and Swedish and uses the EPiServer CMS Language System (lang files) for internationalization. To localize to a new language you will need to edit the XFormSearchGadget.xml file in the site's lang folder.

Please note that the gadget is provided ‘as is’ without any warranty, guarantee or official support from EPiServer. With that said, if you do find any bugs or want to give feedback then that is always welcome by commenting on this blog or by emailing paul <dot> smith [at] episerver {dot} com.

Aug 18, 2010

Comments

Nov 18, 2011 01:11 PM

This just saved me some time. Thanks a lot.

Jan 18, 2013 11:24 AM

Is it possible to override functions in the CMS to alter the Composer XForm Data search page. I have encrypted the data going into the Database but cant find away to decrypt the data when exporting to XML and Excel etc.

Dec 4, 2013 11:58 AM

Does any one ever reply to posts on this forum?

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 |