No error if Key item is set to Number type and Uniqueid is specified as the initial value.

There is no error in the configuration, but a user operation produces a puzzling error.
Is this a bug?

2022-07-04_06h46_50.png

โ€ƒ

2022-07-04_06h45_41.png

โ€ƒ

2022-07-04_06h47_43.gif

2022-07-04_07h18_30.png

Essentially, I believe that the evaluation of UniqueID should result in an error for column types other than Text.
This is especially confusing for citizen developers.

@Steve 
@Koichi_Tsuji 

Solved Solved
6 4 156
1 ACCEPTED SOLUTION

Steve
Platinum 4
Platinum 4

Definitely a bug. Escalated.

View solution in original post

4 REPLIES 4

Steve
Platinum 4
Platinum 4

Definitely a bug. Escalated.

IDใ‚’ใƒ†ใ‚ญใ‚นใƒˆใซใ—ใŸใ‚‰ใฉใ†ใงใ™ใ‹๏ผŸ

number type change text type 

@11148 
That is correct as far as workarounds go.

I believe the problem is that Expression of type Number is not an error even though the return value of UNIQUEID() is text.

As I think about this, I wonder if Expression Assistant assumes that a Text value could contain a value that could be interpreted as a number, so it chooses to defer making a judgement until the column actually has a value. This would actually be in-line with behavior elsewhere in AppSheet. Maybe not a bug; maybe we're just expecting/wanting stronger data-typing than is actually provided.

Top Labels in this Space