How Are You Documenting Non-Romanji Version of Personal Name?

Question

We would like to begin adding the non-romanji, e.g., マホガニー, version of names where they are supplied by our international constituents, in addition to the romanji version of the name, e.g., Mahogany. Before I add custom fields, I wanted to ask if others have simply created custom fields to hold this data, or if you suggest a different approach. Thanks!

@* Sales Cloud - Best Practices * @* Sales Cloud - Getting Started *

Akash Jagdish Gawai · Accepted Answer

Hi Mohogony, If you are implementing the above use case for names only, then I think a custom field is a good and straightforward approach as it is easy to implement, maintain, and query.

Mahogany Lore, MLIS · Answer

We did not end up pursuing this, but ultimately, I had decided to use the custom field I previously created for Preferred Name. Typically we put the constituent's preferred first name in that field and pull it in emails and reports for mail merge documents (letters greetings but not addresses, where we use formal greetings). We would then still have the first and last name to put romanji characters in for sorting and readability by our staff and the post office.

How Are You Documenting Non-Romanji Version of Personal Name?

* Salesforce Essentials *

Más ayuda