- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
On a record producer there is a 'Catalog UI Policy Action' that outputs a message on the form using the 'Field message' value.
Have been asked to translate the value displayed on the form from English to German. I have tried sys_ui_message, sys_translated and sys_translated_text, and nothing seems to work.
Of course I may have made a mistake in what I have setup. However I did wonder if it is actually possible to translate the 'Field message'. Does anyone know if it is possible, and if so how is it achieved?
Thanks in advance
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hello @philrstone
Yes, This is Feasible. I was able to replicate this on my PDI and it works both on the classic view and service portal view.
The Field message (field_message) is a Translated Text field, so only sys_translated_text works. I tried sys_ui_message and sys_translated as well, and neither had any effect.
[Screenshot 1: dictionary entry]
The catch is that the Table name must be catalog_ui_policy_action, not sys_ui_policy_action. The easiest way to get it right:
1.Make sure German is active (I18N: German Translations plugin).
2.Switch your user language to German.
3.Open the Catalog UI Policy Action, enter the German text in the Field message, and save.
The platform creates the sys_translated_text record for you, and your English text stays unchanged.
[Screenshot 2: sys_translated_text record]
[Screenshot 3: portal in German]
If it doesn’t show up right away, run cache.do and hard-refresh. Translation changes didn’t always appear immediately in my testing.
Please mark Helpful/Solution Accepted, if my reply helps.
Regards
Raghavendra G
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @philrstone,
to translate catalog items / record producers, best-practice is to use the ootb Localization Framework artifact for Catalog items,
for all information on how translations work in the platform, please refer to our megathread:
here,
It's not advisable to manually add translations directly to the translation tables or to re-write after a session language change as this can cause unintended side-effects (for example not being captured in update-sets as you might expect - for example inadvertently triggering BR's). I've written quite a few blog posts about this and expected behaviour (all linked in the megathread),
Many thanks,
kind regards
