Skip Navigation

[Resolved] Changing number field to single line

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 7.18 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 1 reply, has 2 voices.

Last updated by Minesh 9 months ago.

Assisted by: Minesh.

Author
Posts
#2685289

Based on prior tickets posted by others it seems there is no way to set a thousands separator on a NUMBER field in Toolset. Is that still true?
What is the impact of changing a NUMBER field to a SINGLE LINE field? Support has previously indicated that it could affect sorting and filtering using a string sort.
But what happens with existing periods (decimal, dot) that exist in the field? Do they remain as they are?
Is there any way other than database search and replace to change a period to a comma in those fields either before or after making the field type change?
Thanks.

#2685541

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Based on prior tickets posted by others it seems there is no way to set a thousands separator on a NUMBER field in Toolset. Is that still true?
===>
- Yes, thats true. You can only add numbers.
- But what we can do is you can add the number value to the number field and we will use custom shortcode to get the value of number field and add thousands separator as required and use this custom shortcode to display the number field with thousands separator.

What is the impact of changing a NUMBER field to a SINGLE LINE field? Support has previously indicated that it could affect sorting and filtering using a string sort.
===>
We do not recommond it.

But what happens with existing periods (decimal, dot) that exist in the field? Do they remain as they are?
===>
No, number field will only accept number. No comma or dot.

Is there any way other than database search and replace to change a period to a comma in those fields either before or after making the field type change?
===>
I do not suggest to change the field type but enter only number to number field in the backend and on frontend as shared you can add the custom shrotcode to display the number field in your desired format.

I hope this does makes sense.