Skip to main content
Solved

Translation of a custom field Aurena

  • December 24, 2021
  • 1 reply
  • 540 views

Forum|alt.badge.img+13
  • Hero (Partner)
  • 155 replies

Hello,

I have created a custom field in APPS10 to display in AURENA.
I added an English and French translation for this field in Enterprise Explorer : 

 


The translation works for Enterprise Explorer but not for AURENA:

 

 

Do I need to add an additional setting to apply the translation on the custom field?
Thanks for your help! 

Best answer by Tuukka

Translations for custom fields shown in Aurena need to be entered separately. Once you have added the field in the Aurena Page Designer and published the updated page, you will get a new entry in Text Translations. You must enter the same translation there, just like you originally entered it in the Custom Field translation. Below is an example of a custom field “NOTES” that I added to Purchase Order page in Aurena.

Please see the Path so you can easily search for your own custom fields. Note that I added my field to the “global” context, so the Path has [global] as the prefix. Each context can have its own translation.

After entering the translation and refreshing the language cache, you might need to unpublish and republish your Page in the Page Designer, so that the fields retrieve their proper translations.

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

1 reply

Forum|alt.badge.img+8
  • Sidekick (Partner)
  • 34 replies
  • Answer
  • December 27, 2021

Translations for custom fields shown in Aurena need to be entered separately. Once you have added the field in the Aurena Page Designer and published the updated page, you will get a new entry in Text Translations. You must enter the same translation there, just like you originally entered it in the Custom Field translation. Below is an example of a custom field “NOTES” that I added to Purchase Order page in Aurena.

Please see the Path so you can easily search for your own custom fields. Note that I added my field to the “global” context, so the Path has [global] as the prefix. Each context can have its own translation.

After entering the translation and refreshing the language cache, you might need to unpublish and republish your Page in the Page Designer, so that the fields retrieve their proper translations.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings