You’re offline. This is a read only version of the page.
Hey,
As of october we are able to select 'do not update form'. This makes sense from certain perspectives, but it would be much better to be able to select which fields to update. For example, some forms could ask for information like 'number of employees'. This is great information that can be supplied by the user, but if they already exist in the system, I only want to update number of employees and not firstname/lastname for example.
(We get a lot off all caps submissions from dubai for example or people only fill the first letter of their name in 'first name'. The form now updates this information if the contact already exists (based on email), but actually makes the record worse because of this.)
Is there a way to stop firstname/last name from updating if the record is matched based on email address?
Hi Niels,
One way, is to use the do not update, and then create a workflow that triggers with a submission, and if contact exists, only updates a specific field (in this case number of employees).
Currently it's not supported directly to select which field would update and which not, therefore setting it to not update and then customizing your choices in a workflow or a Power Automate flow might solve your issue. It is a bit complex, but let me know if you need any help setting that up.
Best regards,
Defne
Hi Niels,
You could refer to following approach:
1. Create other two extra first name and last name fields to Contact entity.
2. Remove the default first name and last name field of marketing form, add the customized two.
3. Trigger a flow/workflow only on creation of contact, sync data from extra fields to the default.
Customers is supposed to submit their correct information at first time, then actual first/last name would be always the original value, only custom fields will update.
Regards,
Clofly
thank you for your response.
Like you said, do not update form is not useful in this situation, because I do want to update contact/lead entities. Just not all of them. (mainly not the basic ones). Our matching rules also only look at email address, so first name shouldn't matter.
I tried to do the same thing as you, but indeed, if i create a new single line of text field, I have to map the fields. This is not the case for an option set. However, now I think about it, this would still not fix the problem. I do want to write information to the first/last name if this is a new contact/lead (just not overwrite it). So I guess that this is unfortunately again a product limitation. (microsoft ideas, here we come ;) )
Hi Niels,
I am test 'do not update form'.
When creating new form field record, can you select other fields of custom entity except the optionset?
I wonder whether the optionset is the only supported field type at present.
And as documentation said, the 'do not update form' will only collect submissions without updating contact.
(My question is if only optionset field of custom entity could be added, then we still need fields such as "first name" and "last name" to identify people, however, when I changed to the single line text field, the two "unmapped" options will be hidden.)
Regards,
Clofly
#1
Hamza H
1,786
#2
Muhammad Shahzad Sh...
1,132
Most Valuable Professional
#3
Abhilash Warrier
351
Super User 2025 Season 2
Share
Report
All responses (
Answers (
