HubSpot Ideas

Msyvrais

Append properties from form submissions

It would be great if we can choose from options for properties in form submissions.

Some we want to replace some we might want to append - this could avoid building a workflow to accomplish the same behaviour.

12 Replies
Msyvrais
Key Advisor

It would be great if we can choose from options for properties in form submissions.

Some we want to replace some we might want to append - this could avoid building a workflow to accomplish the same behaviour.

Akix17
Member

I second this idea! We are running into issues with workflow limits becuase we have so many workarounds for this exact problem.

SBenfield
Participant

Voting for this as well since we have a need to append a contact property instead of allowing a form submission to overwrite the field completely. 

danielrnorris
Contributor | Gold Partner

Yes I am eagerly waiting for the Append feature to be rolled out across HubSpot as a whole. Seems like a pretty big deal for data integrity in a CRM.

HBenham
Member

Yes, we would greatly benefit from this feature as well! 

victoriadubinsk
Member

It would be great to append this! Sometimes the property is cumulative over time and it would be nice to be able to just append information vs overwrite it.

Alysha_TW
Top Contributor | Gold Partner

Agreed, we need this. Tickets can come in multiples, so you need to be able to have the fields for one Ticket record to save on that ticket and for those same properties to populate on the new ticket. Zendesk has it. My clients are saying this gap does not meet industry expectations for Customer Service software.

JMcMinn4
Member

Yes please! I have numerous workflows and reporting issues due to form fields overwriting their previous submission. Would be great to have the option within adding the property to the form to simply check a "append" option so we can capture ALL the data. Thanks!

EKennel
Participant

Here is the temporary workaround we have implemented until Hubspot adds this capability:

 

Form submissions typically have some kind of workflow attached to the backend. So when the Form is filled out, we have a property that captures the data we want (think of it as an inbox), either hidden or not. Then a second property stores all the values (filing the data away), but does not show up in the form.

 

When the workflow runs, it copies the data from the form submission property (inbox), and appends it to the second stored property (file).

 

Hopefully, when "append" is added to the form submission capabilities, we can switch to using the second property that stores all the values in forms without the extra steps.

Alysha_TW
Top Contributor | Gold Partner

Our hack is to not use Records Customization. Instead:

 

1) use Conversations Inbox - the Form submission comes in so you can see all the details.

 

2) If the client wants automated tickets, you can see "Form Submissions" on the Ticket Record.

 

3) If the client wants to use Records Customization, build a workflow on the "Ticket Closed" Status that resets those property fields. 

EKennel
Participant

Using the Conversations Inbox is a good idea for support tickets, but when using lead capture pages, or re-conversion outside of the support hub, The conversations is overkill.

ex. Tracking Marketing event Registration and Attendance. A hidden field in the Form can add the event ID to a contact record, then this event ID is logged in the second property. Automating simple recordkeeping can save the manual effort of checking 100 entries.

Msyvrais
Key Advisor

@Alysha_TW  very creative, but not something that would work in our organization - our form submissions are in the hundreds a month and are all managed through automation and lead assignment rules etc.