Skip to main content
Solved

How can I prevent thousand separator to end up in Excel export?

  • November 20, 2025
  • 4 replies
  • 29 views

In de U-GUI the data does not show a thousand separator for the integer value, as we have not used a numeric control for that column.

U-GUI value

 

Domain setting of specific column


When the data is exported to Excel it however does have the thousand separator set for the cell.

Excel export value


As this value is also used for external purposes by our users, it becomes quite a burden that they have to change the value as that dot (in my case) also ends up in their other program/tool, which is undesirable.

How can i prevent this behaviour from happening?

Best answer by Arie V

@Mark_Plaggenborg please raise this as a bug in TCP on the Indicium product, instead of an Idea. We should fix this!

4 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Mark,

There is currently no way of forcing a text-string to be exported of a field with a numeric (int/tinyint etc.) datatype. To get the desired effect, you would have to store the numeric value as a varchar datatype.


@Mark Jongeling That would be an unfortunate solution if this would be necessary. I am not really thrilled to have to mismatch data types.

Maybe I should have mentioned that this was not the result at the time of development of these types of screens. Somewhere along the line the introduction of the thousand separator happened.

I am not 100% sure, but I think before it was exported the cell would be on “Standard” and now it sets int/numeric fields to “Number”.

Could you check with PI if that is the case and also if that means the thousand separator is technically steerable in such a function?

If so, I can create an idea for that. Thank you.


Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • Answer
  • November 27, 2025

@Mark_Plaggenborg please raise this as a bug in TCP on the Indicium product, instead of an Idea. We should fix this!


@Arie V Will do, thanks. TCP ticket: 13924S