Page 1 of 1

nuNumber field error

Posted: Fri May 02, 2025 3:05 pm
by Uzlander
Hi again, sorry people, probably i'm mission out something but can't comprehend what's wrong with this(nuNumber) field type.
Yes It saves an input to backend but as i touch the configuration section (for nuNumber field), this error pops up.
Reason i'm messing is: List viewed field looks plain while detail viwed looks formatted(as intended), i wanted to both look the same.
Updating didn't solve this

Re: nuNumber field error

Posted: Fri May 02, 2025 3:19 pm
by kev1n
Is the error occurring only for the 'nuNumber' type, or for other types as well?
And does it happen with every object you're trying to save?

Re: nuNumber field error

Posted: Sat May 03, 2025 7:58 am
by Uzlander
Only nuNumber field, but it seems the syntaxerror thing vanished as i shanged the format. Maybe there are some caveats in using 1'000 like format..?
Still the place where i live (one of central asian republics) the local currency unit is nearly 1/13000 of a USD and the number of digits accounted may easily go up to 7-8 n even more, so i clearly need some separator in place.
So i wonder if adding yet another separator (space instead of apostrophe) to existing ones is a possibility, (make it look like 10 350 000, no decimals needed) or we can come up with some workaround? Well generally even an apostrophe symbol is ok for me if its fixed, but space seems even nicer:))

Re: nuNumber error

Posted: Sat May 03, 2025 5:37 pm
by Uzlander
-and i think in case of space separation it should take about 50-70percent width of a character

Re: nuNumber field error

Posted: Tue May 06, 2025 5:31 am
by kev1n
Uzlander wrote: Sat May 03, 2025 7:58 am Only nuNumber field, but it seems the syntaxerror thing vanished as i changed the format.
What was the exact format you used?

Re: nuNumber field error

Posted: Tue May 06, 2025 8:01 am
by Uzlander
well, wonderfully it works now. But generally i think the 'Space' separator would also be a good option if available.
Thank you guys :))