Skip to main content
zorans0426
December 9, 2024
Solved

Implementing Translation Framework for Record Values

  • December 9, 2024
  • 5 replies
  • 0 views

Hello Appian community,

I have a question regarding the implementation of a translation framework on record values in Appian. Currently, we are using database-backed records to store and display various referential data (such as status or list of values). I would like to apply a translation framework to dynamically translate these values into different languages when displaying a grid of record values.

I am concerned about having to create a complex a!match statement to connect these values with Translation Set entries.

Has anyone had experience with this or can provide guidance on the best practices for implementing such a solution using Translation Sets? Any advice or resources would be greatly appreciated.

Thank you in advance!

Best answer by mathieud0001

Hello - I decided to publish a blog post on this subject: https://blog.appiandevs.io/001-how-to-manage-translations-for-reference-data/

5 replies

mathieud0001
December 15, 2024

Hello - I decided to publish a blog post on this subject: https://blog.appiandevs.io/001-how-to-manage-translations-for-reference-data/

zorans0426
June 11, 2025

Hi Mathieu, Apologies for the delayed response.

We had developed a similar translation solution before the introduction of the 24.1 record framework for language selection and translations, though we did not utilize resource bundles.

Thank you for your insights and detailed explanation! Ultimately, we decided against translating values stored in record fields. However, if the need arises, we’ll likely adopt a hybrid approach—leveraging both Appian’s translation framework and our own custom solution.

stefanhelzle0001
December 15, 2024

I try to not store reference values in the DB. Mostly because I need them in the application logic anyways, for assignment and comparison reasons. This means that I now have two places where I need to manage these values. So I stopped using the DB, and just work with constants.

But that does not solve the translation issue and I think that Mat's approach is a great option. And you can still use that reference record together with constants.

mathieud0001
December 15, 2024

Thank you Stefan and excellent point, this approach works with constants as well!

stefanhelzle0001
December 15, 2024

So cool you started your blog :-) Subscribed!