How to bypass integer field formatting i.e. do not need comma separator

[ashwinipingle]

Hello All,

We are using Xanadu and have system property glide.system.locale value as de.AT

When I add an integer field to project form (pm_project table), then after saving, it shows the number as comma separated (dot separated since the system property is de.AT). Is there a way to avoid/bypass this auto-formatting just for this one integer field which is tracking a material number from another system? 

Or do I need to use a text field and allow only numbers in it using scripting.

I am wondering if there is a low-code way to use an Integer field (only number entry allowed) without it adding any commas/thousands separator.  Currently it shows as below.

Best Regards,

Ashwini Pingle

[Ankur Bawiskar · Accepted solution]

@ashwinipingle 

try to add this in the dictionary attribute

format=none

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar · Accepted solution]

@ashwinipingle 

try to add this in the dictionary attribute

format=none

If my response helped please mark it correct and close the thread so that it benefits future readers.

[ashwinipingle]

Thanks for your response, what if this field is shown on report or dashboard or list view or any other view?

Edited - I checked and found that the format is not applied in report/dashboard/list view so this works.

[Maik Skoddow · Accepted solution]

Hi @ashwinipingle 

as you can read on https://www.servicenow.com/docs/csh?topicname=c_DictionaryAttributes.html&version=latest you have to add a dictionary attribute format=none to the field.

Or even better (in my opinion) change the type of the field to string. In my experience, external IDs often include also additional non-numeric characters and if so, your field would be prepared to store them.

Maik