Translation not part of solution

(0) Share

Report

Posted on by ElBarto

Translation of field doesn't get carried over with the managed solution.

Ok, here's the deal. We have a development and test environment. Here again we have a field which is part of a form in the "Contact" entity. Which again is part of the solution. In our setup we have english and swedish language.

We've exported the translation file, done the appropriate translations (and imported it again). It all shows up correctly in the development environment.

When we export the solution (as managed) and import it in the test environment and publish, the translation doesn't carry over for some reason. We've also looked at the xml of the exported solution, and it doesn't seem to be a there.

We've also tried to re-add the field to the form before exporting the solution etc. Without it helping. Does anyone have an idea what can be wrong?

Thank you!

*This post is locked for comments

I have the same question (0)

All responses (17)

Answers (0)

Community Member on at

Like (0)

Report

Hi ElBarto,

What is your UR for CRM 2011?

Do you get any errors during the solution import?

Was this reply helpful? Yes No
ElBarto on at

Like (0)

Report

Hello Oana,

We have UR 15.

No, no errors at all. Everything seems to be fine, but the translation of the field still doesn't change for some reason.

Was this reply helpful? Yes No
Guido Preite 54,086 Moderator on at

Like (0)

Report

the language of this translation is installed inside the test environment?

Was this reply helpful? Yes No
ElBarto on at

Like (0)

Report

Yes, it's correctly installed both on the development and test environment.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi ElBarto,

I have researched internally and the behavior you are reporting might be caused by a bug that was fixed in UR18. Would it be possible for you to apply UR18?

support.microsoft.com/.../2958724

Was this reply helpful? Yes No
ElBarto on at

Like (0)

Report

Thank you for your answer Oana.

We've applied UR18, without that fixing the problem.

The translation becomes part of the unmanaged solution if we export that (it always has), but that doesn't help us. It's a very peculiar problem.

Anyone have any other suggestions?

Was this reply helpful? Yes No
mscrmba on at

Like (0)

Report

Have you seen this Microsoft page?

msdn.microsoft.com/.../hh670609(v=crm.5).aspx

It has the following instructions which may address your issue?

Translating Labels and Display Strings

You can only perform customizations in the application by using the base language. Therefore, when you want to provide localized labels and display strings for these customizations, you must export the text of the labels so that they can be localized for any other languages enabled for the organization. Use the following steps:

1. Ensure that the organization that you are working on has all the MUI packs installed and languages provisioned for languages you want to provide translations for.

2. Create your solution and modify the components.

3. After you have finished developing your solution use the “Export Translations” functionality. This generates a Microsoft Office Excel spreadsheet (CrmTranslations.xml) that contains all the labels that need translation.

4. In the spreadsheet, provide the corresponding translations.

5. Import translations back into the same Microsoft Dynamics CRM organization using the “Import Translations” functionality and publish your changes.

6. The next time the solution is exported it carries all the translations that you provided.

When a solution is imported, labels for languages that are not available in the target system are discarded and a warning is logged.

If labels for the base language of the target system are not provided in the solution package, the labels of the base language of the source are used instead. For example, if you import a solution that contains labels for English and French with English as the base language, but the target system has Japanese and French with Japanese as the base language, English labels are used instead of Japanese labels. The base languages labels cannot be null or empty.

Was this reply helpful? Yes No
ElBarto on at

Like (0)

Report

Thank you for your reply.

That's exactly the procedure we've have followed. As well as removing and adding the field we've changed the translation for in the form (cause this might "force" it to recheck if something has changed).

The problem is that the translation is not part of the exported Managed solution at all (but it is present in the Unmanaged one). Either way, the base languages are the same, as well as the extra language.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi ElBarto,

Sorry to hear the UR18 is not fixing the issue. In similar situations (for German Translations) UR18 was containing the fix to this reported bug.

You said there are no errors. No errors in the UI? Would it be possible to take traces during the solution import?

This is a good tool for collecting traces:

crmdiagtool2011.codeplex.com

First enable just the Error level traces (and disable Verbose).

Was this reply helpful? Yes No
ElBarto on at

Like (0)

Report

I'll look into the diagnostics tool. No errors in UI or export/import of solution.

The problem isn't the import though, it's something with the export. The translation isn't part of the exported managed solution at all.

Was this reply helpful? Yes No