The one thing that really annoys me about Hubspot forms is that you have to create custom property if you want to add a custom field to a form.
We have a lot of different forms, most time for just a short amount of time but with multiple entries by the same client. So we don't want custom properties bloating our contact.
We would like to be able to add an unlimited amount of form fields that isn't connected to a property. Just like you for example can do in Gravity Forms or Formidable Forms.
This data could be saved on the form submission itself or be added to the marketing event attendee (in some cases).
this has come up so many times over the years, like for events where you need to capture meal preferences, etc. and the only solution has been creating custom objects with their own custom properties instead of saving to the contact record. I understand the challenge from HubSpot's pov - without a property, where does this data live in the CRM? and also the flexibility of collecting information that isn't data you would need to report on, filter by, etc.
Imagine I have 10 forms with 10 fields each. I would have to create and maintain 100 Ticket Properties.
Maybe sometimes I just a text or pdf file of the form, which will be created as soon as someone filled the form and stored at their Contact Tab, mapped only with the email.
Some other scenario.. imagine I have 50 products and I want to collect the preferences and the needs (specifications maybe) for each product for each Customer. A mess.
@Jnix284 I would say that the data could live in some kind of HubDB table or a custom event. I would say where you store this information should not hold this functionality back.
This would be such a massively helpful update.....there are many times we want to capture submission data, but don't need it to write to a contact property (or to overwrite contact data). We either end up creating tons of unnecessary/one-time use contact properties which clutter the record, or pushing data to custom objects instead of the contact record (so the CO can contain the clutter).
I am really waiting for this to become a thing.. We have a lot of forms that are used to gather information in a structured way for this particular case. Think of.. ordering a training for example. It's usefull to store some of the info, but it's not necesarry to store the amount of people coming or what timeslot they prefer for the training.
Lots of unnessecary properties.. that also overwrite when the form is filled in a second time. Please let us store the form in full on the Contact record and select what answers should be mapped to a property!
I'm new to HubSpot, but I didn't realize this was an issue until I tried to just add a field for notes and realized I couldn't. My use case is we are meeting people at tradeshows and want to be able to quickly add the new leads to the CRM and make a few notes right on the form without having to leave the form.
It seems to me that if a playbook and an email can be added to the contact record, why can't a form submission be treated the same way and we'd just be able to click on that activity and see the entire form submission. The form itself should be storing the info, not the contact record. If this was the case, we could map anything or nothing to the contact record in a property if we so desired, but the form submission would still show up in the activity feed.
+1 - this would be great to have. We deal with the same issue of "throw away" data clogging up company and contact properties. It makes a mess of things and then other teams get overwhelmed by the number of properties available. I know I can lock down access to certain properties, but this could all be solved by allowing form fields that are unmapped.
+1 - in many cases there is no need to store information in a property. Capture it all and add it to a note on the object activity feed. This makes it filterable and actionable as well without the need for a property for every question ever asked. We opt for Typeform over Hubspot forms + 3rd party integrations to get around this, but it would be great to be able to centralize everything.
Agreed. I need to be able to collect information without tying it to any property. If it must be connected to something, it could just create a "Note" (whereby any text typed in a form field becomes a new "Note" in the Activity Log either for the Company or for the Contact.).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
