Steps to reproduce:1. Add number field to xpage
Set display type → Number
Set display format → Decimal
Add eg. number 8585 to field
Refresh page(Save or do Full Update through action)
Do step 5 again and you’ll get error: Field value is not valid number.
This happens because xpage automatically adds thousand separator to field and therefore value cannot be validated.
Subject: This works for me. Am I missing something…
Here’s what I got
<xp:inputText id="inputText1" value="#{document1.number}">
<xp:this.converter>
<xp:convertNumber type="number"></xp:convertNumber>
</xp:this.converter>
</xp:inputText>
And it works for me. Or am I missing something.
p.
Subject: Number Fields Format Problem - my strange solution
The problem comes with formatting the number.
If I create a number field with no formatting - it works fine.
If I create a number field that has some formatting (which just about all them will have), the problems start.
Here is what happens:
Select Display Format of Custom
Select #,##0
Save the control/xpage
It works fine
… then
Re-edit that field
You will see that the display format has now switched back to decimal but the pattern is still there. But you can not edit it.
If you look at the source - it has type=number in there now. This is not in there when you select custom.
Resave the control/xpage
The field will no longer work correctly. If the user enters #,### it will fail.
The real crazy part is for existing data - it will display in the format you specify, but when you save it - it must be without the commas. So you can not resave your forms without removing commas from all number fields.
To band-aid it - I entered a javascript formula for the number format. It seems to be working. Here’s the code I used to make it work:
<xp:inputText value=“#{doc.numField}” id=“numField”>
<xp:convertNumber type=“number”>
xp:this.pattern</xp:this.pattern>
</xp:convertNumber>
</xp:this.converter>
</xp:inputText>