We have another client that uses a web-form with many options (similar to a survey).  In this case they didn’t want to see all of the form fields in their system or need the result saved in a structured database. They simply needed to view the data as part of the contact’s history.

Their solution was to capture the form elements containing data into a single Note Activity via the API:

The note format looks something like:

They also have ~100 form inputs, but if the person that submits the form only chooses 5 or 10 inputs that’s all that’s seen in the attach note.

That’s a cool idea although I think there will be benefit for the data to be stored in a database for other reasons for us… Are you aware of the toolset they used to implement the form?

The form was simple HTML (hand crafted) and they modified the sample “Contact Us” API script to catch the POST and save the records to Solve.  Yes, once the data is moved to a note you’ve lost the opportunity to get it into a DB structure, but I thought I’d toss it out there as an example.

Thanks. I suppose I need to build the survey, however (ruby, html, bla, bla bla) send everything to a SQL db and send what I want Solve to hold there.

It would really help to be able to have project blogs with different form fields on them. That way I could create a template FORM area for a blog and thus host more fields than I normally want to deal with for that set of projects.

Bryan