web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Dealing with bilingual lookups and optionsets in CRM

(0) ShareShare
ReportReport
Posted on by 290

Hi all,

I am looking for the best practice in CRM 2013 to deal with optionsets and lookups in both English and French languages. Solutions that I have played with so far are either merging values both languages in one line (not acceptable by the client) or using JavaScript to filter items based on language (unsupported approach).

To make everything more difficult, the CRM deployment is supposed to be integrated with an external legacy system that only understands one key/ID and translates the value based on the user language on the legacy system. I would appreciate it if you share your experience or give me some pointers that can help dealing with the bilingualism issue in CRM.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    ScottDurow Profile Picture
    21 on at

    Option sets can be translated by exporting translations and then re-importing - see www.zero2ten.com/.../crm-2011-online-localization-custom-translations

    Lookups are a little trickier. One option is to add the second language as an attribute and show this in the lookup view and also add a quick view form to the form to show the second language - but you can also use an approach similar to my technique shown at - www.develop1.net/.../Multi-Language-Lookups.aspx

    Hope this hells,

    Scott

  • Mohammad Atif Profile Picture
    on at

    Can you please see https://community.dynamics.com/crm/b/develop1/archive/2013/01/05/multi-language-lookups.aspx if that is helpful.

    Regards,

    Mohammad

  • Suggested answer
    Reza Farahani Profile Picture
    290 on at

    Thanks Scott for the detailed answer. Certainly now I have a better idea on how to deal with lookups. Your blog is great and I'll definitely give it a try with your approach as it makes a whole lot of sense to me. The solution for optionsets seems work fine for the CRM user interface (although it is unsupported) but not sure if it works for our integration purposes. Happy new year!

  • Reza Farahani Profile Picture
    290 on at

    Thanks Guido for the expert advice. You're right about the bilingual requirement in Canada and the fact that most clients here do not accept merging values in one field.

    Happy new year!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans