Storing Webform Results Within Profile (repeat) [#732904]

This questions was asked a year ago #455070: Storing Webform Results Within Profile and there was promise of a solution in 3.0.

I am just enquiring if there was a solution or a workaround to store the completed results in %profile[key].

Comments

Comment #1

quicksketch

he/him

CreditAttribution: quicksketch commented 4 March 2010 at 22:29

Category:	feature	» support
Status:	Active	» Fixed

The solution was to use Views for your listings, which could be placed anywhere. See #273837: Views Integration for Webform and #680386: Views integration for the webform_submitted_data table. Marking this "fixed" as a support request, though it's more accurately a duplicate of those two issues.

Comment #2

waverate CreditAttribution: waverate commented 5 March 2010 at 15:35

I am not sure if I would call this question solved.

It sounds like, from the two references, that the workaround was not to store the results in profile_values but to leave the results in webform_submitted_data and display the results as a view. I believe that the results view would only be of submissions for now as the view of the data is still being worked on.

The drawback of this is that for a multisite with shared user and profile tables, you would have to share the webform table as well. Unfortunately, this is all webforms not just the one that updates profile data.

Did I read your response correctly?

Comment #3

quicksketch

he/him

CreditAttribution: quicksketch commented 5 March 2010 at 16:20

I might not be understanding what you're trying to do. You're trying to update a user's profile based on Webform submissions? Webform isn't really intended to do things like update users or nodes, and there aren't any plans to map Webform fields to profile fields.

Comment #4

mileZ CreditAttribution: mileZ commented 5 March 2010 at 16:25

Hi Waverate,

you can do that with the Content Profile Module.

mileZ

Comment #5

waverate CreditAttribution: waverate commented 5 March 2010 at 17:59

Milez,

I saw that but I was hoping not to create user nodes. It also seems that content_profile has a finite lifespan.

quicksketch is correct in that webform is not intended on updating user profiles. After thinking about, the profile module already has the ability to create or edit a user profile through its own forms. We can then check these fields in the webform and if there is missing mandatory information, send the user back to edit the user profile. We then only need to store the uid and any additional fields that are not part of the profile.

Thanks for both your help and I would love to hear if you have any more ideas.