I am Dutch and in Holland we often use an inbetwwen name, it’s called “tussenvoegsel”. In the CRM Hub i have created that field and the data from the importfile is present after the import is finished. In the record it is oke but the header of the contact is not changed.
Contacts full name is Michiel de Ruyter but it is displayed as Michiel Ruyter.
The most common thing that I see is to include within the Last Name property. So in the example:
First Name: Michiel
Last Name: de Ruyter
If you want to take this approach, you can download your data and in excel, concatenate the two properties with a space in between the two columns, and then re-upload.
Would there be any negative consequences of incorporating this into the last name field?
Thanks for tagging, @Josh! I would’ve suggested the same.
@TDijkstra, is the tussenvoegsel usually captured in the first or last name field or is it a separate form field on Dutch pages? And what role does it play in the saluation – Mr de Ruyter or Mr Ruyter?
If you need it as a separate HubSpot field, then it’s probably easiest to just accept that HubSpot has no UI option for this. You would still be able to personalize your emails – it just wouldn’t show up on the contact record.
Global applications such as HUBSPOT should be perceived that the whole world is not an American culture and that each country has peculiarities in communication, which is a very sensitive issue.
That’s why you need to improve on things like this and not look at it from the SW’s point of view that it’s just an additional complication with the new field.
Thank you so much for your valuable feedback. We appreciate it.
I would like to suggest that you post this feedback in the Ideas Forum as it’s monitored by our Product Team. The Ideas Forum is the best place to communicate with the team.
There is no problem to make the adjustment as mentiond in both your solutions, the only thing i have to aler is the import file and join the data in both the fields before import the file.
What we do is put the middle name into the Last Name field. Your communication will be correct. The tricky thing here is that you can’t use automatic Workflow formatting or the new Data quality tooling. This because this would capitalize the middle name, which is wrong. So far I’ve found no workaround to fix this automaticly so this means you have to manually correct Last name formatting. The new Data Quality tool helps you indentify any incorrect last names that include a middle name though.