You’re offline. This is a read only version of the page.
50
I have following issue with the localization of FSM:
1. We have 3 FS orgs with base language EN and language pack DE
2. On all 3, there is Woodford with the FSM project
3. We have done a lot of translation changes in the DEV org, Field Service works perfectly, the FSM connected to the DEV org shows all labels correctly as they were translated
4. We export and import the field service solution from DEV to one of the other org
5. Field Service application shows all labels correctly
6. We export and import the FSM solution from Woodford from DEV to Woodford to one of the other orgs
7. Part of the FSM labels is translated, part is not, for example the main screen labels on FSM are not translated
8. As as workaround, we export also the language file from the Woodford mobile project from DEV and import the file into Woodford in the target org, which brings the missing labels to the correct values.
But even with these steps, the translation file in Woodford in the target is showing in the column "Organization" the wrong, standard label values, only in the column "Project", there are the correct translated values. In the DEV however, in both of these columns, there is the correct translation value. Seem like Woodford is ignoring translation coming from an imported CDS customization file.
Any idea, what is wrong here?
Hi Robert,
It is difficult to answer you about this, but it seems that could be an issue/bug in the way that woodford are dealing with the translation.
I believe that the best approach here is to raise a Support Ticket with Microsoft and show us the behavior, because this issue is quite specific.
Best Regards.
Thank you for using Microsoft Dynamics 365 Communities,
community.dynamics.com/.../dynamicscrmsupportblog
Dynamics CRM Support Engineer - Customer Engagement
Microsoft
Share
Report
All responses (
Answers (
