Instead of the javascript, maybe you can set the destination of this screen action to "Current Screen" instead of an end-node. It would in essence, do the exact same as your javascript. 

You could also store the user's preference for a current locale, and add it to the OnApplicationReady event.

Hi Hector!

I don't think refreshing the entire page would be necessary. You could fire an Event from the Menu webblock instead, and simply refresh the data in the Event Handler action. You could also handle any further element refreshes from there.

Hi Hector,

Just to let you know that is a known issue that will be fixed soon. 

The workaround Monique mentioned (triggering an event in the menu and changing the locale on the event handler, instead of doing it in the menu) should do the trick. What you might be missing is that you need to change the locale on the event on the page, instead of doing it on the menu. For this the event needs to send the locale as a parameter.

Cheers,
Tiago Simões

Hi @Hector Piza, 

We were able to confirm that your scenario is part of the known issue that will be fixed with the next release of the Platform Server in early March (Platform Server 11.11.1).

Regarding the workaround, we have concluded that, for now, the approach you had of forcing a page to reload after setting the new locale is necessary to affect the table headers.

Thanks for sharing the issue and help us improve this capability.

Regards,

Vítor Teixeira