Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics CRM (Archived)

Translation not working

Posted on by 189

Hi,

has anybody ever had the phenomenon that a translation made in the CrmTranslations.xml is not working after importing it?

Even if I check the value in the database directly per SQL it looks ok, but another value is shown in the application on the form.

Our Scenario is:

Main language: german

Second language: english

The german value is shown on the form correctly, the english is not.

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Translation not working

    I m also facing the same issue.

    Main language is English and  second language is Spanish.  when i exported the translations, it contain translations for every field in English as well as Spanish. but it i don't know why it is not reflecting.

  • Hikmat Daghestani Profile Picture
    Hikmat Daghestani 170 on at
    RE: Translation not working

    I was editing my answer, check it out again.

    What exactly are you trying to translate?

  • KaiHartmann1981 Profile Picture
    KaiHartmann1981 189 on at
    RE: Translation not working

    Did you also have Problems with the translations?

    As I am experiencing these problems as early as in our development environment, all I do really is to export/import the translations, there are no yellow signs unfortunately.

  • Suggested answer
    Hikmat Daghestani Profile Picture
    Hikmat Daghestani 170 on at
    RE: Translation not working

    I'm having the exact same problem. I would appreciate a better feedback than which I'm about to give.

    1- If you mean translations related to option-set (as in a drop-down list), then you should include all relevant global option-set *Optionsatz* in the solution then translate.

    2- I think  there are elements in a solution which causes CRM to skip/prevent applying some other following elements. Which elements exactly? I don't know, but I solved this problem once by removing workflows/processes from the solution before translating and publishing it. It worked at the time, but today it isn't sadly. I guessed that processes could cause a problem with translation publishing due to warning signs in the publication phase overview. So if I were you,  I would check those warning signs and try to remove them from the solution.

    3- You could also try to create a solution which includes only the entity you're trying to translate. 

    Regards 

    Hikmat

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans