HubSpot Ideas

AVara

Lock fields from overwriting new data

I have a field where I would like to capture data when a lead is created, but I don't want that field overwritten when the lead takes additional actions. Today, the field is overwritten if I can add it as a hidden field on forms. 

 

It's been recommended to create a workflow intead of a hidden field, but we already have so many workflows, it would be easiest to just add the field to the form(s). 

14 Replies
hchristian
HubSpot Employee

Upvoting on behalf of a customer 🙂 This is a great idea especially in order to avoid creating an extra workflow to accomplish this goal.

MartinK
Contributor

I read this as we need a feature to lock fields from being overwritten by subsequent forms submission.
Once a form has been submitted, there needs to be per field option to lock the content or else subsequent form will overwrite the fields with every submission. Not every field on the form, but selected fields. This would work for progressive form as well.
The reality of forms is that the info provided is often sloppy and needs to be edited of sorts. ie. a contact submits his credentials as John Doe but with an email addres of Suzy.Fowler@xx.com. We can safely assume that the contact is called Suzy. So we change the contact name to Suzy. Unfortunately, with the next forms submission the the name is set back to John Doe, Darn!

Having a lock on the field to prevent further update after intialisation would definetly help!

PLEASE!!


ameliak
Member

Couldn't agree more - really need this feature! We have people thinking they're registering new people in a form, and registering using the same email address - so the details keep on being overwritten - it's a nightmare to manage

MRask
Member

This is a huge issue for us. We are onboarding people with a form - details are overwritten every now and then as HubSpot somehow connects new contacts with existing companies.

VEspo
Top Contributor

This would be huge for us too!  Possibly even give an IF/THEN option ... if the field is already populated, just display in the form, otherwise give them a field to fill in

VEspo
Top Contributor

or I should say ...

 

having an option to set a field to "only update if that field isn't already populated in their record ... if the field is already populated, ignore updating from the form, otherwise update it once the form is submitted.

 

We can't use the pre-populate solution given elsewhere as we have a lot of family members using the same computer.

 

NTunnicliffe
Participant

We were actually told by a HubSpot prefferred suplier during the set up of our HubSpot marketing suite that this would happen and built around the idea that a property would never be overwritten and instead populate with multiple answers - this has recently been shown as incorrect and is causing a lot of issues. So really frustrated that HubSpot nor the 3rd party supplier was able to prewarn us of this

MLaBorde3
Member

Agree! We are new to HubSpot and track what programs our clients participate in as a multi-checkbox property. Our application for programs are obtained through forms, so when they apply for a program it will overwrite their past program participation. We are currently manually entering each time a client participates in a new program. 

LStoichkova
Participant

During the set-up of our HubSpot marketing suite this would happen and built around the idea that a property would never be overwritten and instead populate with multiple answers - this has recently been shown as incorrect and is causing a lot of issues. So we really need this feature! We have people thinking they're registering new people in a form, and registering using the same email address - so the details keep on being overwritten - it's a nightmare to manage

AshishDaga
Member

Now it's Aug 2023. Any solution/workaround for this issue? 

I'm facing a similar issue and the previously entered field value is getting overwritten.  I wish at least it provides options to update a few fields. Ex: Comments, descriptions. Previously entered data in these fields wash out if the same user submits the form again with diff info in these fields. 

 

VThorogood
Member

I think I have the same issue here. I used to use Vutu.re and there was the ability to make form fields read-only. So you could pre-populate for the intended recipient. Disallowing someone who was forwarded that email/link to LP to overwrite possibly creating duplicates - and indeed completing an RSVP as an un-invited person. This is causing me to have to rely on if then branches in workflows to match against existing lists and then allowing or not accordingly. A lot of bother that would be saved by simply allowing a form field to be a read-only situation (with maybe a link to a blank form if the situation required it) 

LSørensen
Participant

I agree with Vespo on this one:

"having an option to set a field to "only update if that field isn't already populated in their record ... "

 

We were going to start using a form for customers applying for an account, but probably have to stop the process, as we've discovered it overwrites critical data if the system finds a match (so far, they haven't been true matches). We've found we would risk the invoicing data of a company to be overwritten depending on the match Hubspot makes.

That is in no way a helpful form.

So if we could get some way of putting it on hold for a check before it was allowed to update data, or even could set it to only update field with data if the field is empty, that would be really helpful.

ngan
HubSpot Employee

Comment on behalf of my customer: We 100% need this feature and more flexible options to lock a property from being overwritten by different processes. It will help control the sources that are allowed to edit certain properties.

AVara7
Participant

Replying to this idea as this came up again today. 

 

It would be great to have the ability to mark a custom field as Read-Only or locked. Not just for form submissions but for list imports or workflows. I have a workflow where I add a datestamp when a contact enters the workflow. That information is then passed to another database for reporting purposes. I don't want the original datestamp overwritten in Hubspot or the other database. So I have to branch where datestamp is know, skip to another branch, or proceed down the branch where the blank field would be updated.