Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Translation not part of solution

(0) ShareShare
ReportReport
Posted on by

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

  • Muhammad Naderi Profile Picture
    135 on at
    RE: Translation not part of solution

    same here, any progress?

  • Community Member Profile Picture
    on at
    RE: Translation not part of solution

    We have the same issue as u ElBarto. The translations are stored in the unmanaged solution but not in the managed. Have you ever found a way to solve that behaviour.

    Best Regards!

    Lukas

  • ElBarto Profile Picture
    on at
    RE: Translation not part of solution

    Seems like the exact same problem indeed. We don't have the opportunity to use and unmanaged solution either. It shouldn't be necessary, cause this should work?

    I didn't find any relevant information from the tracelog from the diagnostic tool, but that might be because I don't know exactly what I'm looking for.

    The best workaround we've found is to just copy the translation from the exported unmanaged solution to the managed one. But, it's still a workaround.

    Are we running out of options here?

  • Community Member Profile Picture
    on at
    RE: Translation not part of solution

    this article describes exactly, what I'm allready doing. Sadly the most important step:

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

    does not work.

    Why: Because there are no translated components (at least components on the forms) in the exported managed solution.

  • Community Member Profile Picture
    on at
    RE: Translation not part of solution

    Hi,

    Can you please check below link. It might be helpful.

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

    Mansoor

  • Community Member Profile Picture
    on at
    RE: Translation not part of solution

    I do have exactly the same issue on the newest 2015 on-premise. Same procedure, no translations in the managed solution. A deployment with unmanaged solution is no option for me.

    I'd love to have a solution for this very annoying problem! My current workaround: make the translations on each environment (export on TEST, replace excel values with translation file from DEV, and import the translation file again on test, publish). But this workaround sucks, especially when you need to do this for each solution update...

    ... there must be a better solution for this!!!

  • Community Member Profile Picture
    on at
    RE: Translation not part of solution

    Aside: Are you intending to distribute this solution, as an ISV, or free for the community?

    If not, why would you want to get yourself stuck with a managed solution? For internal dev work, I would always advocate using unmanaged solutions to deploy between environments eg dev > test > production

  • ElBarto Profile Picture
    on at
    RE: Translation not part of solution

    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.

  • Community Member Profile Picture
    on at
    RE: Translation not part of solution

    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).

  • ElBarto Profile Picture
    on at
    RE: Translation not part of solution

    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.

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

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,261 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 233,009 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans