Possible Bug: Number("") is not working as expected

NUMBER("") expression is not working anymore as expected and as described in the linked doc.


1 Like

Yes it shows the zero with the gray color, but when you save the record, I believe it doesn’t show or save any value… not even the zero.

3 Likes

@Aleksi,
Earlier the behavior was not like that. It was showing just a blank value, not even a greyed out zero like this. Besides, the doc is comletely inline with the previous behavior but now it also contradicts as well provided that behavior had been changed.

2 Likes

Why would you like to use the initial value with the NUMBER("")? The result is the same with or without it.

Simply I don’t want a value to be appearing as zero, even if it’s a ghost value indicating that the field is a number field or requires a numeric value.

Earlier; if you leave the initial value blank, the field was already appearing like this in the form view. Then upon some requests, NUMBER("") expression brought to use. And there are several post I remember that both you and I and many others have replied with use of NUMBER("") expression in the initial value to whom was asking how to eliminate that zero initial value.

So as to say, I’m not pretty much interested with the result. I’m interested with the UI.

3 Likes

I too prefer a field like this to remain blank. In some instances, a 0 in a field could actually mean something vs. a blank.

4 Likes

Absolutely! The UI should not indicate a specific value will be assumed when it won’t be.

3 Likes

We also prefer the ability to set the initial display value of a Number field to a blank / empty value. We are still not finding this to be an option.

Attn @Arthur_Rallu

2 Likes

We actually received complains from app users, claiming the placeholder for number type field is currently showing 0 which looks like initial value or acutal 0 value is already placed, and not really assinting user what to do with such a field.
At a glance, it looks like 0 was initally placed upon opening new form.
Better not to show this, or better to give us, app creator to place our own placeholder for each of entry field on the form view.

This is not an ideal workaround, we twisted “description” setting with IF expression to guide app user to place number for such a fields until we get the permanent solutions.

4CF85330-8532-4836-ACD7-B2D416C66DF4

@Takuya_Miyai

@Arthur_Rallu

3 Likes

Not collecting much of interest, but current appsheet UIs for input is not really helping app users.
Not able to apply prefix/suffix, and no control over the placeholder neither.

Matrial UI is providing property to control the placefolder, why dont we take it for Appsheet to give us more hands to control over?

@Arthur_Rallu

@Takuya_Miyai

1 Like