That is very weird. Just tried it in a test app, I also get the wrong number returned in the same way. However if I change it to a Text type column it returns correctly.
Please inform your tables structure, how many tables you have and what are their column names and types and the designated key for each table. Is there any relation between the table?
I have not tested but my one guess is if the field is retained as a number field ( 18 digits) , then the number is too large to be handled as a number type field by AppSheet number definition?
So is it possible that it truncates some digits?
Probably it needs to be treated as a text and tried with lookup formula?
Hi @Heru As a side note of interest, my testing showed that even numbers are returned in LOOKUP() expression, eventhough I agree with you that the syntax suggests it to be a text literal.
It’s different that my test. My test using number over 15 digit always return the rest of the numbers truncated as 000. I was suspecting that it has something to do with excel limits of accuracy 15 digit, but your result shows differently.
Hmmm… something wrong with me.
I have just made a test with google sheet. The result is the same as previous test, however, I found that when test using expression assistance, it shows the correct number. as below snapshot. However, in the emulator and google sheets, when the type selected is number, it shown with truncated number (after the 15 digits).
You are correct, even I am finding on close obervation that the number truncates on saving. But in case of Google sheet, only the last two digit (18th Digit and sometimes 17th digit ) seem to be truncating.
Even though earlier test results had shown otherwise.