System text translations not always processed

0
I'm translating an app, and I've come across a couple of system texts that have been accidentally incorrectly changed in the past.After changing the text, saving the document and restarting the app (locally), I didn't see the new text.I didn't just re-run, but actually stopped and started the app, I even cleared cookies, closed Studio Pro... but nothing.The strange thing is, this does not happen for all system texts. I tested this with changing the 'Password policy - Invalid Password' message, and after rerunning the app, the new text was visible.My issue seems to be specific for Message dialog texts, like the title of the warning/error/confirmation dialog windows.Does anybody have an idea what could cause this issue and where these texts might be cached or something?
asked
1 answers
0

Hi Martin,

I've run into something similar before, particularly with Message dialog texts (warning, confirmation, error dialogs).

My experience is that not all "System Texts" are treated equally. Some are evaluated directly from the model and reflect changes after a restart, while others appear to be bundled into the client resources and don't always refresh as expected after a simple Run.

A few things I'd try:

  • Delete the deployment directory and run the app again. Sometimes client resources are not regenerated as expected during incremental deployments.
  • Hard refresh the browser (Ctrl+F5) and/or test in an Incognito window.
  • Check whether you're testing with the React Client enabled. I've seen differences in client-side caching behavior between client implementations.
  • Verify whether the text is truly coming from System Texts and not from a Marketplace module or custom widget that happens to display a very similar message.

One clue is that:

Password policy messages update correctly, but dialog titles do not.

That makes me wonder whether the dialog titles are being cached client-side or loaded from a different resource bundle than the validation messages.

As a diagnostic test, I'd:

  1. Change the warning/error dialog title to something very distinctive.
  2. Delete the deployment directory.
  3. Run locally.
  4. Open in a completely clean browser session.

If it still shows the old text, I'd start looking at whether the dialog is actually using the system text key you changed.

I've occasionally seen inconsistencies where a system text appeared unchanged until a full deployment directory cleanup was performed, even though other translations updated immediately.

I'd be curious whether anyone else has seen this specifically with the built-in dialog titles, because those seem to behave differently from many of the other translatable system texts.


answered