CRUD Support with Forms application

There are ways to do this but you have to really think about security and is the person updating the form the person who submitted it. Or don't you care if the person updating is the person who submitted? Also, forms don't require you to be authenticated to fill them out so you'd need to have a mechanism for checking that as well.

What I've done in the past is created a custom webpart which looks up the form data by the form definition and form data's GUID. There are some checks in there as well for permissions as only a few people are allowed to view, update and delete those records (not the original submitter).

Thanks Brenden,

The Forms will be on pages that require the contact/user to be authenticated and I figured I may need to store the ContactID in the form data as well.

So to your knowledge there is no "Built In" way to achieve this easily? This is the conclusion I've come to in my testing and searching.

Given that, it sounds like mapping form fields to contact fields may be the best approach.

Thoughts and thanks again!

Jeff

So I'll ask, why do they need to edit the form again? Maybe this will help understand what can or can't be done.

Well, for example, if we wanted contacts to be able to edit their profile.

One possibility is allowing them to select from a group of products they are interested in: Pianos, Drums, Guitar, Bass, Vocal ... We would like to track if they are interested, play, own products in each of these categories. Later we would use this type of information within the marketing application.

While this small example could be tracked using custom contact fields, I'm just wondering what the possibilities are with using only on-line forms.

Thanks again for your time.