# Always keep multiple HubSpot Properties (DropDown) values in sync

**URL:** <https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848>\
**Category:** Tips, Tricks & Best Practices\
**Tags:** professional\
**Created:** [January 29, 2024, 8:01am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848 "2024-01-29T08:01:41Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![deltaglider](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@deltaglider](https://community.hubspot.com/u/deltaglider)\
**Post date:** [January 29, 2024, 8:01am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/1 "2024-01-29T08:01:41Z")

</div>

Hello everyone,

Unfortunately, since HubSpot does not offer localization of the DropDown Properties, I have to create language aliases for several properties (DropDown).

Example:

Salutation\_EN {Mr, Ms}

Salutation\_FR {Monsieur, Madame}

My challenge is, how do I keep this in sync (bidirectional) with a workflow that is as simple as possible?

Thanks!

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [January 29, 2024, 8:05am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/2 "2024-01-29T08:05:45Z")

</div>

Hi @deltaglider,

For properties used for salutation, I’d recommend approaching this differently:

1. Create a property “Gender for salutation” with options “Male”, “Female”, “Non-binary”
2. Use the property from step 1 in your website forms
3. In the website form editor, rename the options corresponding to the language of the form, e.g. change “Male” to “Mr” directly in the form by clicking the pencil icon next to the option. This change will only apply to this form. When submitted, the value will be stored as “Male”.
4. Use a workflow to translate “Male” in each language, e.g. if “Gender for salutation” is “Male”, then “Salutation\_EN” is “Mr”. Do the same for all other gender options and languages and expand the workflow.
5. Use your “Salutation\_EN”, “Salutation\_FR” properties for personalization in marketing emails.

That way, you have a single source of truth for gender - and only use your other properties as a result of looking up the gender. That bypasses the issue of checking which one is known, copying it to all others etc.

It’s cleaner from a data management standpoint, less prone to error and by default avoids all conflicts (e.g. EN set to Mr, FR set to Madame).

Best regards!

---

<div class="post-metadata">

**Author:** ![deltaglider](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@deltaglider](https://community.hubspot.com/u/deltaglider)\
**Post date:** [January 29, 2024, 8:20am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/3 "2024-01-29T08:20:32Z")

</div>

Hi @karstenkoehler ,

Thanks for your suggestion.

You are absolutely correct: In the case of forms that I’m embedding on websites your suggested solution is the way to go. However, I’m in need of multi-language options for using in sales templates where I can’t edit the dropdown options.

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [January 29, 2024, 8:21am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/4 "2024-01-29T08:21:58Z")

</div>

@deltaglider for the sales templates, wouldn’t you then use the “Salutation\_EN”, “Salutation\_FR” properties? I don’t see a conflict there.

---

<div class="post-metadata">

**Author:** ![deltaglider](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@deltaglider](https://community.hubspot.com/u/deltaglider)\
**Post date:** [January 29, 2024, 8:28am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/5 "2024-01-29T08:28:11Z")

</div>

Thanks @karstenkoehler! Could you help me find the easiest workflow step to achieve that? My context is that I’m having multiple (\>7) properties with 3 language “versions” each. Combined I’m \>100 drop down options that I need to sync. Is using a workflow the easiest solution for that?

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [January 29, 2024, 8:31am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/6 "2024-01-29T08:31:17Z")

</div>

@deltaglider could you maybe explain the bigger picture in a bit more detail? What are those other 7 properties? What’s the third language? Which use cases do you need this for? Are the sales emails sent manually or automatically from sequences via workflow?

I’ve set up portals for \>20 languages with correct salutation and automation. This is possible and it’s possible to do this very smoothly. The exact steps depend on what you’re planning to do with this.

---

<div class="post-metadata">

**Author:** ![deltaglider](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@deltaglider](https://community.hubspot.com/u/deltaglider)\
**Post date:** [January 29, 2024, 8:53am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/7 "2024-01-29T08:53:08Z")

</div>

@karstenkoehler, The big picture is that I’m using the property values to go into an sales offer email that I’m sending out to prospects. As I’m dealing with potentially 3-4 target languages I’m storing a number of offer options in deal/company/contact properties in multiple languages. Salutation was just one simple example, others are different model types in the respective languages, etc. The sales team shall use the “Master” property in the HubSpot view, in the background the other language alias should be used to feed the other language sales email templates with the right drop down values. Does this make sense?

---

<div class="post-metadata">

**Author:** ![deltaglider](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@deltaglider](https://community.hubspot.com/u/deltaglider)\
**Post date:** [January 29, 2024, 8:36am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/8 "2024-01-29T08:36:57Z")

</div>

The big picture is that I’m using the property values to go into an sales offer email that I’m sending out to prospects. As I’m dealing with potentially 3-4 target languages I’m storing a number of offer options in deal/company/contact properties in multiple languages. Salutation was just one simple example, others are different model types in the respective languages, etc. The sales team shall use the “Master” property in the HubSpot view, in the background the other language alias should be used to feed the other language sales email templates with the right drop down values. Does this make sense?

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [January 29, 2024, 8:43am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/9 "2024-01-29T08:43:46Z")

</div>

Hi @deltaglider,

I don’t see a lot of complexity then. The approach here would be to maintain one source-of-truth-property that is only used internally and displayed in English, such as “Gender for salutation” with options male, female, non-binary.

You would then use a workflow to translate this into your three languages. With seven properties, this comes down to seven workflows with three branches each, and one action per branch; doable, I would say.

For your sales emails, I’m still missing the context how exactly you’re sending these. But essentially, you would create a EN template that references the EN properties, a FR template that references the FR properties and the same for the third language.

In summary, your team would maintain central properties, translated by workflows. Templates then reference the translated properties.

I would strongly advise against maintaining language properties directly. It is not possible to keep these in sync in a clean way while also avoiding data conflicts. It is also a much worse user experience when it comes to entering the data.

Best regards

---

<div class="post-metadata">

**Author:** ![deltaglider](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@deltaglider](https://community.hubspot.com/u/deltaglider)\
**Post date:** [January 29, 2024, 9:00am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/10 "2024-01-29T09:00:12Z")

</div>

Thanks @karstenkoehler, you’re confirming the option that I’m also seeing as the only viable from different perspectives.

In the sales emails I’d use the respective language properties, i.e. for an English email it would be Salutation\_EN, whereas for a German Email Salutation\_DE.

I was hoping that HubSpot offers an easier way of achieving this. 🙂

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [January 29, 2024, 9:02am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/11 "2024-01-29T09:02:10Z")

</div>

@deltaglider I don’t think waiting for a better option from HubSpot is not the right approach here - requirements are too nuanced for there to be the perfect solution.

I’m convinced you’re on the right track with my proposed approach. Again, I’ve implemented this for international companies with many more languages and properties, it’s solid, it’s been running well for years and it meets all requirements.

---

<div class="post-metadata">

**Author:** ![deltaglider](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@deltaglider](https://community.hubspot.com/u/deltaglider)\
**Post date:** [January 29, 2024, 9:22am UTC](https://community.hubspot.com/t/always-keep-multiple-hubspot-properties-dropdown-values-in-sync/98848/12 "2024-01-29T09:22:20Z")

</div>

Thanks for your help, @karstenkoehler !
