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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Using Easy Translator ...
Customer experience | Sales, Customer Insights,...
Suggested answer

Using Easy Translator brings fields into unmanaged layer, even when they were not edited during translation

(0) ShareShare
ReportReport
Posted on by moko33 1,788

We use Easy Translator from XRM Toolbox to do some translations. If we export translations, only adjust one single field, than reimport translation file, we're getting lot's (if not all the fields in the file) into the Active Layer. Why is that?

What is the best way to avoid that? I guess always delete all rows from translation excel file which you don't want to edit...?

I have the same question (0)
  • Nya Profile Picture
    Nya 29,060 on at
    RE: Using Easy Translator brings fields into unmanaged layer, even when they were not edited during translation

    Hi,

    If the issue has been solved, it would be appreciated if you could click "Yes" to verify my answer.

    Image

    If there is any further doubt, please do not hesitate to let me know.

  • Suggested answer
    Nya Profile Picture
    Nya 29,060 on at
    RE: Using Easy Translator brings fields into unmanaged layer, even when they were not edited during translation

    Hi,

    As the Easy Translator is not an OOTB feature but a tool provided by XrmToolBox, it is recommended to ask the provider for further help.

    Easy Translator  · XrmToolBox

  • moko33 Profile Picture
    moko33 1,788 on at
    RE: Using Easy Translator brings fields into unmanaged layer, even when they were not edited during translation

    Thanks for the reaction.

    I still don't know if this is a bug by Microsoft.

    The problem is as following:

    having only two fields in translation-file, only adjusting one field, leaving the other as it was, than importing the file.

    This results in both of the fields going from managed layer into active layer. Even if I have purposely changed only one of the two fields.

  • Suggested answer
    Nya Profile Picture
    Nya 29,060 on at
    RE: Using Easy Translator brings fields into unmanaged layer, even when they were not edited during translation

    Hi,

    Do you mean that the importing process will take a long time if the xml file contains all the translations?

    If yes, the solution you mentioned - always delete all rows from translation excel file which you don't want to edit can help.

    It is not necessary to include all the fields when importing the translated xml file.

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

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft
Our Community Code of Conduct has been updated!

Quick Links

Responsible AI policies

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

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Daniyal Khaleel Profile Picture

Daniyal Khaleel 122

#2
DAnny3211 Profile Picture

DAnny3211 101

#3
Abhilash Warrier Profile Picture

Abhilash Warrier 70 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans