[BUG 7305] Perspective Table Number format not changing according to the selected Locale

Ignition
1

Hello,
I am using Ignition 8.1.23 and facing right now an issue with number formatting inside the Table. When i change the current locale to one using ',' as decimal separator, the number format remains with '.' as decimal separator.

image
image1427×684 65 KB

so i created a view containing on top a NumericEntryField with the format property not set to none, and below of it a table. Now when i change the locale, the number format of my NumericEntryField is updated and as a side effect of that, the number format inside my table update as well. This keeps working event if i hide the NumericEntryField as long as its format property is define. So for me it seems like the perspective table component is not able by itself to trigger the number format process. This means for me that i will always have to have a hidden NumericEntryField on my view to be sure that the format inside the table sweet the selected locale. In that case it will look for me like a bug.
It is also possible that i am missing something. Therefore i will be thankfull if you can tell me if it is really a bug or if/what i am missing.
Thanks in advance for you help

2

Thanks for bringing this scenario to our attention, I have since opened an internal bug for this issue.

3

Thanks for describing your workaround. This is still necessary on 8.1.29.

4

I am glad that my workaround can help someone else than me :wink:

5

Is there a resolution to this problem? I have tested a perspective table in 8.1.43 and I still have the same problem. When changing locale the number format does not change with the chosen locale.

6

No, the problem is still present

7

Hello team, when does this gets resolved? Please we face this issue for de-DE and also for hu-HU locale. Only locale it-IT seems to be working perfectly for number format.
The bug has been there since 2023

8

Make a support ticket, asking to be added to the notifications for the bug in the title. This does two useful things:

  • It helps IA know how many users are suffering from this bug, so IA can prioritize it properly, and

  • It automatically puts you on the list to be notified when the bug is resolved.

9

Hi @pturmel thank you for the reply.
Yep I have done that last year.