Using CRM with Asian languages (Simplified Chinese, Korean, Japanese) RRS feed

  • Question

  • Hello, I have a requirement from a team of UK-based CRM users who work with contacts in Asia (mostly China, South Korea and Japan). They would like to be able to store Asian characters in CRM (contact and account names and addresses) and be able to search on the 'romanized' version and display the original script. The users speak and can read one or more Asian languages and would prefer to read the contact's business card details in the original script (because the card's romanized translation isn't always accurate). We're planning to scan the business cards into a file which will be imported into CRM via a spreadsheet.

    Since they want the CRM user interface to remain in English, I don't think any of CRM's language packs are required, but I was wondering about CRM's support for non-roman character sets. It is as simple as importing the Asian script into an alternative name field? Is this what the Yomi Name fields are for -- I've never seen their purpose documented anywhere.

    Does anyone have any guidance or advice they can share?

    Thanks, Neil
    Monday, January 4, 2010 2:52 PM


All replies

  • I have checked in past that the datatype of the fields in backend database is nvarchar. So you should be good to save the data in foregin languages. ( As far as i think).

    Monday, January 4, 2010 3:03 PM
  • Hi Neil,

    You can check out Frank Lee's blog 

    CRM database supports multi-languages.

    I hope this helps.

    Darren Liu | 刘嘉鸿 | MS CRM MVP | English Blog: http://msdynamicscrm-e.blogspot.com | Chinese Blog: http://liudarren.spaces.live.com
    • Marked as answer by Jim Glass Jr Monday, January 4, 2010 3:25 PM
    Monday, January 4, 2010 3:24 PM
  • Thanks Darren. All my afternoon of Binging and Googling didn't find this article -- you're a much better source of knowledge than either!

    With a bit of testing, I've managed to import a company from a Excel spreadsheet saved as a Unicode text file. I thought the CRM import wizard could only deal with .CSV files (which can't be exported from Excel with Unicode encoding), but it turns out that it can handle .TXT files saved from Excel in Unicode text format.

    Now all I need is the IRIScard for CRM and IRIScard Asian combined into one, and to add a few extra fields to cope with Asian and Romanized versions of names and I'm all set.
    Monday, January 4, 2010 5:00 PM
  • While CRM will support Asian languages (I've imported Chinese, Korean and Japanese in the past), there are assumptions regarding the given name and family name and how these are displayed for contacts i.e. the family name coming last in a full name, which is not necessarily valid in the Asian context. Also the A-Z filtering on the bottom of the Contact list screen is all but useless if you are putting the Asian name into the first and last name fields.

    Mostly these are inconveniences and not show-stoppers as a lot of western systems have these issues and Asian workers are used to it.

    I read somewhere a long time ago that Yomi is for the western version of an Japanese name but I have no idea where I saw it.

    Leon Tribe

    Want to hear me talk about all things CRM? Check out my blog


    or hear me tweet @leontribe
    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    • Proposed as answer by Leon TribeMVP Monday, January 4, 2010 8:33 PM
    Monday, January 4, 2010 8:33 PM