I don't see a decimal seperator on my iPhone numeric keypad

I Have a field with a price property, and when I want to enter a price on my iPhone, I see this keypad:


the funny thing is I don’t see a decimal seperator.

Is this a iPhone issue or do I need to change some settings?

Regards,

Ralph

1 Like

How do you have the column defined? Which iPhone are you testing on?

If you tap the “+*#” in lower left, do you see the decimal separator then?

There are settings within the device to customize keyboards. Nothing jumped out at me that would control the type of keyboard shown.

I have an iPhone 7 and tested Number, Decimal and Price fields in an app. I get this keyboard below. I haven’t needed to do anything to make that happen.

The column type is “Price”
when I tap the “+*#” button I see this:


so it look like a phone keypad
I have a iPhone 7 to
Strange thing is:
I added a new column in my Google sheets and added some numbers in it.
And now I se a normal keypad like a calculator and back to my old bedrag field: I see the phone type keypad the one you see in my first post.
and both the old and new number field has the type price

strange

I’ve escalated this internally.

Ah I found the issue
When I go to the properties of that column I added the value 25 at this field:
Increase/decrease step
when I change that back to 0, then I see my calculator type keypad.
When I change it back to 25 the I see my phone type of keypad

I’m having the same issue. I added a couple new columns and tried to give them a price type instead of decimal. Now, no matter what I do it comes up with a phone keypad instead of an alphanumeric keypad.

I am also getting this error: “Column Name ‘Labor’ in Schema ‘Jobs_Schema’ of Column Type ‘Number’ specifies an invalid ‘Precision’ 0. Precision must be greater than zero.”

Where and what is precision? I’ve been able to manipulate things to get rid of the error but still the phone keypad makes it impossible to enter decimal values, even when the type is set to “decimal”

1 Like

Whoa! That’s definitely unexpected behavior! I strongly encourage you to engage support@appsheet.com to report the apparent bug(s?) and get help.