In Pivot Table JS functions, we are forced to use the localized name of a property, even if not using the “localizedName” for a property, it is taken from messages.properties file.
Sample project attached: invoiceLine.date returns null while invoiceLine.DateLoc returns the date correctly. (DateLoc is defined in the messages.properties)
Which means the code outcome depends on what you have in your messages.properties files, this is dangerous.
If a user connects with another locale, pivot is broken. If one day a client asks to change a display label for a field, same. And I did not test with labels containing spaces, which obviously can happen in localizations.
If “localizedName” ought to be the solution, it means localization is hard coded…
This is not developer friendly, and, worse, I wonder how we can use this component in a multi-language application.
Or am I missing something ?
testcuba.zip (158.8 KB)