Hello,
I have a problem with the translation of custom fields. I've done everything based on the documentation and posts from this forum, but unfortunately the translation I've entered doesn't work. I tried to unpublish from page designer and it didn't work either. Please support me.
Solved
Translation of custom field
Best answer by tofuse
Hi,
I think that you got some good help above, I will just add some extra details here.
When you have added a field or made label changes to some field. You navigate to ‘Translatable Texts’. You should not go to ‘Text Translations’ first, because there might be none for the item you search for. ‘Translatable Texts’ contains all items that can be translated, regardless if they have translations or not.
Filter Configuration Translatable Texts
-
Module: Configuration Items are always saved for module
CONFIG. -
Main Type: Client configuration items will have the main type
Configuration Client -
Layer: Configuration items are saved in the
Userlayer. -
Path: The path for the translatable item contains important components.
-
Configuration Context: The first part of the path enclosed in brackets (e.g.,
[global]) represents the 'Configuration Context'. -
Client Model: Follows the context. For example, in configurations for the client model
Customer, this part helps in filtering relevant items.
-
-
Prog Text: You can also search using a specific prog text value.
When you have identified the translatable item you want to translate. From here you can open the ‘Text Translations’ window that will filter existing translations for the item. Add translations is easiest done by invoking the ‘Add Translations’ command.
Refresh Language
After adding or changing translations, you need to refresh the language cache for the metadata to pick up the translation changes. This is done from the ‘Text Translations’ window.
Additionally force refresh of metadata cache
Note: There is a bug in this area that can trip you. When changing configuration in Page Designer or making changes to translations. The metadata cache is invalidated. Next time you go to the page new version of metadata is built and cached, but translations is fetched from the last time the language cache was refreshed. Unfortunately, the metadata cache is not invalidating metadata cache. So you need to do this in the order. Make translation changes → refresh language cache → re-visit the page. If you or someone else is visiting the page after you did your translation changes, these changes will not be included in the page. This is why this last step in Karales info make sense. This will invalidate the metadata cache.
- Open the page in Page Designer again, unpublish and publish again
+11Hi,
have you refreshed the language cached? sometimes browser cache after too.
Best Regards,
Wasana
Hi,
I refreshed the language cache and now I also refreshed browser cache - nothing has changed. If you need any screenshots or more explanation feel free to ask. I really need to solve that issue.
+11Yes please can you share the translation text page screen shots.Hope you add translations for page designer fields. not the LU custom fields?
/Wasana
+11Hi,
This is LU custom field translation.
You need to add translation for the field you added in page designer which is shown in client.
Best Regards,
Wasana
+11Hi,
It should be under translateble texts something like this. May be you can search from prog text.
/Wasana
Hi,
I have translation here also but it still doesn’t work. Could the reason be that the Path column does not find my context?
+11Hi,
Did you add the column to page using page designer? after its added there should be a line here in translatable text shown with that path to page. there you need to define translation to show in page.
Best regards,
Wasana
+11Hi,
can you see the field in web page? As per your screen above i can see that your page is behind(the warning sign in light orange) that you need to merge?
Best Regards,
Wasana
Hi,
My mistake, I corrected it, now I see that my context appeared, but it still did not solve the problem.
And now column Cena jednostkowa should be translated to Unit price and it isn’t
This works for me:
- Add the column to the page via Page Designer, save and publish
- Go to Translatable Text andf find your page designer specific field (set search parameters: Layer = User, Prog Text = "~YourField")
- Find the entry where Sub Type = "Column", click Add Translations and add your translations. The “Path” should start with “[global]”.
- Go to Text Translations page and view the translation you just added
- Click on your record and select Refresh Language Cache → By Path and Children
- Open the page in Page Designer again, unpublish and publish again
I guess (hope) there is a way to translate the fields on a global level, so you don’t have to do it for every page designer addition, but this works meanwhile.
Hi,
I think that you got some good help above, I will just add some extra details here.
When you have added a field or made label changes to some field. You navigate to ‘Translatable Texts’. You should not go to ‘Text Translations’ first, because there might be none for the item you search for. ‘Translatable Texts’ contains all items that can be translated, regardless if they have translations or not.
Filter Configuration Translatable Texts
-
Module: Configuration Items are always saved for module
CONFIG. -
Main Type: Client configuration items will have the main type
Configuration Client -
Layer: Configuration items are saved in the
Userlayer. -
Path: The path for the translatable item contains important components.
-
Configuration Context: The first part of the path enclosed in brackets (e.g.,
[global]) represents the 'Configuration Context'. -
Client Model: Follows the context. For example, in configurations for the client model
Customer, this part helps in filtering relevant items.
-
-
Prog Text: You can also search using a specific prog text value.
When you have identified the translatable item you want to translate. From here you can open the ‘Text Translations’ window that will filter existing translations for the item. Add translations is easiest done by invoking the ‘Add Translations’ command.
Refresh Language
After adding or changing translations, you need to refresh the language cache for the metadata to pick up the translation changes. This is done from the ‘Text Translations’ window.
Additionally force refresh of metadata cache
Note: There is a bug in this area that can trip you. When changing configuration in Page Designer or making changes to translations. The metadata cache is invalidated. Next time you go to the page new version of metadata is built and cached, but translations is fetched from the last time the language cache was refreshed. Unfortunately, the metadata cache is not invalidating metadata cache. So you need to do this in the order. Make translation changes → refresh language cache → re-visit the page. If you or someone else is visiting the page after you did your translation changes, these changes will not be included in the page. This is why this last step in Karales info make sense. This will invalidate the metadata cache.
- Open the page in Page Designer again, unpublish and publish again
Hey,
Thanks for you accurate answer. I wonder why if I enter Translatable Text page i cannot see path divided to specific context. When i enter this page I can see only something like this:
There is no more contexts even if i have 2 of them.
Is there any chance this long-standing bug could be addressed? It seems to affect many superusers.
For example, could running Refresh Language Cache potentially invalidate the metadata cache?
- Here’s an example of the question that highlights the same issue 3 years ago: https://community.ifs.com/framework-experience-infrastructure-cloud-integration-dev-tools-50/translation-of-ifs-cloud-custom-fields-23537
- I noticed the same issue even during the Academy Training.
(IFS Cloud - Experience Tailoring - Custom Objects Configurations (Virtual Blended Course) Day 4. time: 2:25:25
Hey
The problem was in my approach. I was going to Translatable Text directly through the button and oddly enough, it was only pointing me to one context. As I found the attribute manually - it showed me all three contexts and the translation worked. Many thanks to all participants for their help.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.