All topics

Formatting numbers larger than 3 digits don't show up?

Armand

6 months ago

I am formating numbers (not set as currency) to show:
IF <1 -> first few significant digits
ELSE -> min-maxfractiondigits 2

And numbers like 0.000724 show up fine, but anything that is 1000 or more does not show up.

Please have a look at the video for more info:
✅1
Tom Ireland

6 months ago

Hey, Armand. I couldn’t tell immediately from the formula if anything was wrong (I’d need to watch again), but you don’t have any max length set on the input do you? A good one to check first to see if that attribute is set.
Tom Ireland

6 months ago

Ignore that 👆🏻- you can see the length is good based on the video. 🤔
@Tom Ireland
Ignore that 👆🏻- you can see the length is good based on the video. 🤔
Armand

6 months ago

Yes, that should not be the issue. I'm starting to wonder if it's a bug, having digged around here a bit more: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/NumberFormat#significantdigitsfractiondigits_default_values
Tom Ireland

6 months ago

I don’t know much about significant digits, but I just watched https://youtu.be/pplQ5hphgj0 and it could be the value that is returned in some cases has a higher number of significant digits than your max. Could that be the case?
@Tom Ireland
I don’t know much about significant digits, but I just watched https://youtu.be/pplQ5hphgj0 and it could be the value that is returned in some cases has a higher number of significant digits than your max. Could that be the case?
Armand

6 months ago

Good watch that video.

I don't think that is the case though, because I only apply min/maxSignificantDigit IF the value is less than 1.

IF the value is not less than 1 I use min/maxFractionDigits.
Armand

6 months ago

Also seems to be working fine here.
Armand

6 months ago

It seems to be happening as soon as I introduce the Format Number node.
Without that node numbers of 1000 and greater show up without any issue.
even without an options object, but with a Format Numer node the issue is present.
And it occurs on any input I use (type Number). So it is also not caused by my input component.
Armand

6 months ago

✅ Update: I have found a solution

Solution: Set the input type to text instead of number

It's a bit weird that this was the solution, especially since I was only using numbers in these input fields. I'm not sure if I should report this as a bug.
Tom Ireland

6 months ago

I think I’ve spotted the issue. It looks like the If statement operators are set to a string instead of a number. The same in the Set as well. If you change the type to number, does that fix it? You can click the little dropdown and change to Number. Would probably also explain the reason why the change in input type worked.
@Tom Ireland
I think I’ve spotted the issue. It looks like the If statement operators are set to a string instead of a number. The same in the Set as well. If you change the type to number, does that fix it? You can click the little dropdown and change to Number. Would probably also explain the reason why the change in input type worked.
Armand

6 months ago

Oh good one! I hadn't thought of that. Let me give it a try
👍1
Tom Ireland

6 months ago

I’d check all aspects of your formula where text may be output instead of number because that’ll likely have some effect if not intentional.
@Tom Ireland
I’d check all aspects of your formula where text may be output instead of number because that’ll likely have some effect if not intentional.
Armand

6 months ago

I did. And everything except Locale, Path and Objects is set to number. However, I ran into some funny business again.
@Armand
I did. And everything except Locale, Path and Objects is set to number. However, I ran into some funny business again.
Tom Ireland

6 months ago

Hey! Thanks for sharing. I was just spinning up an example to recreate the issue and noticed that your currencyValue object was set to:

{
"eur": "",
"thb": ""
}

Could this be the source of the problem? I assume they need to be a number, so would explain the NaN when changing parts of your formula from string to number.

The currencyValue should look like this if set to number instead of an empty string:

{
"eur": 0,
"thb": 0
}

I'll keep having a go to see if I can make some headway.
@Tom Ireland
Hey! Thanks for sharing. I was just spinning up an example to recreate the issue and noticed that your currencyValue object was set to:

{
"eur": "",
"thb": ""
}

Could this be the source of the problem? I assume they need to be a number, so would explain the NaN when changing parts of your formula from string to number.

The currencyValue should look like this if set to number instead of an empty string:

{
"eur": 0,
"thb": 0
}

I'll keep having a go to see if I can make some headway.
Armand

6 months ago

I changed that (and then the other parts as well again), but to no avail.

Please don't put too much of your time into this. I know you got plenty of other cool things you are working on. And I got something that is working for me now (with the 'type: text').
@Armand
I changed that (and then the other parts as well again), but to no avail.

Please don't put too much of your time into this. I know you got plenty of other cool things you are working on. And I got something that is working for me now (with the 'type: text').
Tom Ireland

6 months ago

Yeah, you're right - there is something odd going on. Even making sure everything is set to number correctly results in the same problem you're experiencing. I think it is to do with the format number options. If I look at the result of the currencyValue where I input 100000 into the TBH input, I see:

{"thb":"100000","eur":"2,739.75"}

But the value of the EUR input shows nothing.

It's okay re time - I like to help out.
Tom Ireland

6 months ago

I think I worked it out. When inputting a value like 100000 into the TBH field, the result is 2,739.75. Note the comma, which is a string value. So, changing to text works because the "number" is actually a string.
@Tom Ireland
I think I worked it out. When inputting a value like 100000 into the TBH field, the result is 2,739.75. Note the comma, which is a string value. So, changing to text works because the "number" is actually a string.
Armand

6 months ago

So that’s why is has to be ‘type: text’? Would make sense why greater than 999 doesn’t work.
@Armand
So that’s why is has to be ‘type: text’? Would make sense why greater than 999 doesn’t work.
Tom Ireland

6 months ago

Correct. Unless there is an option for the number format formula to help with this, you'd probably need to use Matches with a regex to deal with the comma.
@Tom Ireland
Correct. Unless there is an option for the number format formula to help with this, you'd probably need to use Matches with a regex to deal with the comma.
Armand

6 months ago

Probably a bit more complex than is worth it for this use-case. But definitely good to know for the future!
@Armand
Probably a bit more complex than is worth it for this use-case. But definitely good to know for the future!
Tom Ireland

6 months ago

Yeah, interesting to dive into. I found that the useGrouping option when set to false for the number format should remove any separators but could not get it to work.
@Tom Ireland
Yeah, interesting to dive into. I found that the useGrouping option when set to false for the number format should remove any separators but could not get it to work.
Armand

6 months ago

Yes, I just gave that one a go on my end as well, but nope.
Tom Ireland

6 months ago

Team toddle or toddle-hero’s - anyone know why setting ”useGrouping”: false in the options object for Format number doesn’t work? Armand is getting a string value returned in an input because the currency conversion contains a thousandth separator (comma). He has to set the input to text for it to display the value when using minimumFractionDigits and maximumFractionDigits as another option. I thought ”useGrouping”: false would mean it remains a number but it doesn’t work. Is that a bug or are we not understanding it correctly?
Erik Beuschau

6 months ago

It seems we don't pass the useGrouping parameter correctly in the Format Number formula atm. I'll have a look and let you know when it's supported 👍
@Erik Beuschau
It seems we don't pass the useGrouping parameter correctly in the Format Number formula atm. I'll have a look and let you know when it's supported 👍
Tom Ireland

6 months ago

Wahoo! @Armand ☝️
👍1
@Erik Beuschau
It seems we don't pass the useGrouping parameter correctly in the Format Number formula atm. I'll have a look and let you know when it's supported 👍
Armand

6 months ago

Thanks Erik!
@Tom Ireland
Wahoo! @Armand ☝️
Armand

6 months ago

And thanks Tom for helping with this!
👍1
Erik Beuschau

6 months ago

useGrouping is now supported. You might need to refresh without cache though to get the new version of the Format Number formula 👍
@Erik Beuschau
useGrouping is now supported. You might need to refresh without cache though to get the new version of the Format Number formula 👍
Tom Ireland

6 months ago

Nice one, Erik. 🙌🏻
@Erik Beuschau
useGrouping is now supported. You might need to refresh without cache though to get the new version of the Format Number formula 👍
Armand

6 months ago

Perfect! Works like a charm 🙌
🙌2

Formatting numbers larger than 3 digits don't show up?

Armand

Tom Ireland

Tom Ireland

Armand

Tom Ireland

Armand

Armand

Armand

Armand

Tom Ireland

Armand

Tom Ireland

Armand

Tom Ireland

Armand

Tom Ireland

Tom Ireland

Armand

Tom Ireland

Armand

Tom Ireland

Armand

Tom Ireland

Erik Beuschau

Tom Ireland

Armand

Armand

Erik Beuschau

Tom Ireland

Armand