Translation of component parameter does not work

[Johan18]

Hi

The translation feature and components features are great, however they do not work properly together which impacts our development speed. If we could just use the translation feature as we do for graphical components we would be very happy.

Sending a translated string as component parameter does not work and just outputs the norwegian (in our case) value for all languages.

Therefore we need to this. Needless to say this causes a lot of work when we need to change a button, since we are now translating to all the languages available so we need a check for every language inside a function…

This has been reported in the spring and is a headache for us. We would also like to be able to send enum with an icon and use that icon in the button, this does not work either).

Can you update on where you are on this, is it on the roadmap (if not then why) and when can we expect a solution? I actually consider this a bad bug as it seems to be supported in the app but just does not work.

Regards,

Johan

[Simona]

Hi @Johan18,

Thanks for the detailed write-up.

For the translation issue: this is a known challenge, and we already have it reported internally. We can’t promise a timeline right now since we need to balance many requests and bugs, but I’ll make sure to add your input to the prioritization. Your example really helps illustrate the impact.

Regarding the enum + icon setup: I tried it out on my side and it seemed to work. Could you share a bit more about your setup (maybe with screenshots)? That would help us reproduce it if there’s a specific case where it fails.

Appreciate you taking the time to report this!