The strangest thing happened to us recently – one that really blew my mind. I’m going to spare you the long road of trial & error we went through to come up with the answer – or at least an explanation of what cause the behaviour.
Because “a picture tells more than a 1000 words” .. let me just show you. In the below images, you see the language (Dutch) in green – and you see English (which is not set) in red.
How strange is that?
On top of that – there is no code whatsoever that I can influence the wrong parts.. .
On top of that – there were other databases that were correct: same client, same everything, different database.
We tried a bunch: Windows updates, upgrade client, remove metadata, recompile, … you name it!
After long consideration .. and after a golden tip of my colleague (aka punky), we discovered it had “something” to do with a certain rolecenter. After starting to disassemble the rolecenter, we discovered the root cause of the misbehaviour is …
Chart parts !
I hear you .. say what? Indeed. From the moment you have a chart part on your role center – no matter which way (by development or by customization/personalization) .. it starts to behave like that. So all you need to do is remove it from the role center, and languages will behave decently.
That’s it for now – next – I’ll be enjoying my birthday … 🙂
Happy Birthday and thanks for sharing
And a question for the day after: Do you have any clue if 365 BC (on premise) will still get a Windows Client?
As far as I know – it will have a windows client indeed. But do know that there is a focus in abandoning it, when functionality reaches parity…
Thanks for sharing this issue.
Do you know or Microsoft did deliver a solution for this problem? Because removing the charts is not really a solution because a customer of ours uses them a lot.
Or is there any other solution for this?
at this point, i’m afraid not…