Hi,

- First , create a user control for input of form data. It's the user control that takes care of storing data in the database (plain old asp.net...).

Either user control and code behind file go into /usercontrols folder, or in case of a compiled assembly, dll goes into /bin folder and ascx user control in /usercontrols folder.

- Create another user control that will serve as a dashboard control - that user control will list data stored in the database (which has been submitted through the form)

Again, upload user control to the umbraco install (you're free to choose where to upload in this case, but would advice to also use the /usercontrols folder.

Register the dashboard control in /config/dashboard.config

[code]

[/code]
(Names can/should be changed of course according to your implementation)

Feel free to ask more questions if not clear...

Cheers,
/Dirk

EWatkins,

Another way round this would be to create form as document type then use doc2form to render the form and store the form submission as node in separate part of the site under a root node. Make that node only accessible by admin. You could view items in the content tree.

If you still want separate dashboard access to view then create a dashboard control with repeater on it use nodefactory to get items below that node and return them as datatable (method on node factory to return children as datatable) and bind to that. You could quite easily hack the code in doc2form to do the logging.

Regards

Ismail

@Ismail: I'm confident your solution works out great, it will, but will create lots of overhead if data is stored as "documents" in umbraco. It would only take up space in the content xml (and more memory in case of big response...) which you'd avoid in a large and popular site?

(Btw, I've also done it a couple of times the way you describe it, mea culpa. Not longer now...)

Just my 2 cents

Cheers,
/Dirk

Dirk. Interesting. I like the idea of storing all kinds of data as Umbraco-documents, but I understand that it might cause overhead like you say. But - if one stores the specialized data-documents in another nodebranch than the main content nodebranch, would that help to keep overhead smaller?

mysite / content / ...

mysite / all-kinds-of-data / ...

@prgjonas: Nope, unless you don't publish the 'all-kinds-of-data' documents.

Cheers,
/Dirk

@dirk,

I have actionhandler setup to prevent publishing of form submissions, its private data i dont want it published thus its not in content xml. I also have subfolders in the form folder eg processed, spam. I also have tab on the form doc type called status that has drop down with statuses that map to folders so in my example the drop down would be spam, processed user can then select a status and save and actionhandler drops it into appropriate folder. As part of training the system admin is given guidance on clearing out old form data or moving it into appropriate folder.

It depends really how much data your going to get the doc2form way is nice quick way of getting a form up. In the past where I have had to deal with large volumes of submissions i have gone down your suggested route and used subsonic scaffold as dashboard control for admin purposes.

This is what i love about umbraco there is always more than one way to skin a cat!

Regards

Ismail

I have set up everything and I can get the form to write to an xml log file and display almost everything. To do this I modified Warren's contact form that comes with the cws, however I am having one small issue. Everything shows up fine in the xml, but one field is not being translated from the xml to the dashboard. I can see the field populated in the xml but I can not seem to figure out why it will not populate in the dashboard. I think the fields for the dashboard pull from logscript.js and this is what I have in there:
$(".asset .formlogs li").click(function() {

var logName = $(this).find("ul li.name").text();
var logPhone = $(this).find("ul li.Phone").text();
var logAddressLine1 = $(this).find("ul li.addressLine1").text();
var logAddressLine2 = $(this).find("ul li.addressLine2").text();
var logEmail = $(this).find("ul li.email").text();
var logMessage = $(this).find("ul li.message").text();

$(".asset .displayLog span.name").text(logName);
$(".asset .displayLog span.Phone").text(logPhone);
$(".asset .displayLog span.addressLine1").text(logAddressLine1);
$(".asset .displayLog span.addressLine2").text(logAddressLine2);
$(".asset .displayLog span.email").text(logEmail);
$(".asset .displayLog span.message").text(logMessage);


//Remove selected class from previous item
$(this).parents().find(".asset .form_logs li.selected").removeClass("selected");

//Add selected class
$(this).addClass("selected");

return false;
});

Everything but Phone comes through. Any ideas?

Solved it, had to reload the cache!

is working on a reply...