Autocomplete in editmode



I am about to implement an autocomplete function on a textbox in edit mode. If this was episerver 6 i would have written a custom property where i would include a user control with all the functionality i needed.

But this is Episerver 7 and we're using MVC. What is the best approach to do this? 

- A custom property? How would do build that with MVC?

- Editor descriptor? Can you include jQuery functionality into that or do you have to use this Dojo-thingy?

- Another option?



May 27, 2013 17:32

Check out my blog post that basically shows how to implement this:

May 27, 2013 18:12

Thanks. I will look into it.

May 28, 2013 10:09

I made your example work now after hours of cursing.... :)

Turned out that the objects you return from the rest service need to have a name and an id, not a name and value. Big thanks to Tomas Eld who wrote that in the comments.

Also, I must say this approach was really hard. I would never have solved this without your blog post. Is there any good resources that explains more how Dojo is used in Episerver 7 or something? How is one supposed to know that you need a new config file and 3 javascript files that define a lot of external files/namespaces, both dojo/dijit but also epi stuff.

For instance, what is 


and how should i know that I need them? Is there any documentation about this?

Anyway, thanks again!

May 28, 2013 16:34


First of all, I updated the blog post to use Id. I guess that this might have changed in the 7.1 upgrade since we upgraded to Dojo 1.8 in that release.

Regarding documentation about how to work with expanding the UI, there exists some documentation, although we still lack a lot of information and samples, specifically for the EPi client API. The information that exists today is:

Information about the user interface in general, for instance an introduction to Dojo and further referenses to get started:

Client Side API-documentation for CMS:

Client Side API-documentation for the Framework parts:

Me and some other people have also written blog posts about this, for instance:


Regarding future improvements, we are currently working on improving the format and content for the client API documentation. I also hope that we will create a separate UI-project for CMS where we can put some common functionality to be able to implement common scenarios without having to write any client code at all. More info to come about this when we get closer to the next major release...

May 28, 2013 17:31

We actually use 7 and not 7.1, but we will soon upgrade. I guess some stuff might break then :)


Thanks for the links! 

May 28, 2013 17:38
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.