SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

A long title but hopefully will be enough! Basically, I want to create a feture in Visual Studio that will do the following: When activated, places an option/link in the site collection options in Site Actions. This link will then open a page with a completely different user interface page that has several selectable options for the user. Say for example the user selects a list and some fields or other options and those selections will be stored somewhere (this is what I really want to know how to do). Then the user will "Apply" the settings and this action will then render custom content in a custom delegate control stored in the master page. I know it sounds like a webpart, but I have seen many of these things and they do not look like webparts and there are no webpart zones. I believe they are custom controls which I have built before and I have built custom delegate controls. I am wanting mainly a cool user interface that runs on the SharePoint page and somehow stores the options and this is global at the site collection.

Whew! I tried to be as detailed as possible, but I am just not sure what the correct terms are for some of these things. I have built custom application pages and that may be what it is, but I just do not know how to store the selected options so that they are then used to create the HTML that will be placed in the delegate control.

EDIT: A good example to a point would be Nintex Workflow or something similar. Though I am not trying to build a workflow tool. I know it creates a workflow, but it also stores the settings and user selections that create the workflow and it has a great user interface. That's what I would like to have for my custom tool.

Any thougts or suggestions are appreciated!

share|improve this question
up vote 1 down vote accepted

I think, given that the changes are 'global', you could simply use a list to store them, at root level.

So on the root level of your sharepoint site, create a list (that you hide from navigation etc), with a content type that has all the fields you need to store.

Then, when the user 'saves changes' from your custom page (or control), that list is updated or added to.

The webpart or control or page that uses the custom settings can then access that list on Load.

share|improve this answer
Though this is not what I was hoping to do, there is technically nothing wrong with this approach and I should be able to hide the list just fine. – spevilgenius Nov 1 '12 at 18:55
glad to be of assistance ;) – Mahendran Govender Nov 2 '12 at 12:18

You can use SPPersistedObject which stores data in Configuration database. I have written a blog post which shows how to use SPPersistedObject in admin pages in SharePoint. This may give you some pointers on how to use it in your page.

share|improve this answer
This might be an option but I am not sure if I could then read that information to render content in a delegate control from the stored settings. – spevilgenius Oct 28 '12 at 17:47

I had similar requirements and I preferred to store custom settings for each user in a hidden list called user info list.

More information about this list here:

I extended the list by adding an extra column to store the user settings.

share|improve this answer
This is more of a global solution and changes would only be for the settings of the solution. The end result is to draw specific html in a delegate control. – spevilgenius Oct 28 '12 at 17:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.