Error editing table with different error codes

Hello Everyone, I hope you're all doing well.

In one particular table in one particular app I'm facing a strange problem, where it is not possible to edit any row after being created. Action buttons than change column values just do nothing when clicked, while the Edit button shows an error with a different error code each time it is clicked. 

This behaviour is consistent across different browsers, different users and among the Editor, Mobile and Desktop views. Things that didn't help include: regenerating structure, changing the data source, removing columns, etc.

AppSheet support has been investigating with no outcome yet. They made me make a copy of the app for them to investigate freely since I'm having problem in a production one. Interestingly, the copy is having the same problem. 

Please tell me if you had a similar issue in the past. I'll update you as well with any feedback from support. Thanks.

Some screenshots and details about the error: 

Capture dโ€™eฬcran 2024-03-12 aฬ€ 04.36.13.pngCapture dโ€™eฬcran 2024-03-12 aฬ€ 04.36.27.pngCapture dโ€™eฬcran 2024-03-12 aฬ€ 04.36.55.pngCapture dโ€™eฬcran 2024-03-12 aฬ€ 04.37.09.png

 

Error id: 8226

Stack: TypeError: Cannot read properties of null (reading 'basestType')
    at b (https://www.appsheet.com/assets/66aa69d7b3241cd0537457156d984eeb70a8f7c16b5f4da6ef6e7f3bf5cf9827.js:1:591102)
    at https://www.appsheet.com/assets/66aa69d7b3241cd0537457156d984eeb70a8f7c16b5f4da6ef6e7f3bf5cf9827.js:1:591038
    at Array.map (<anonymous>)
    at b (https://www.appsheet.com/assets/66aa69d7b3241cd0537457156d984eeb70a8f7c16b5f4da6ef6e7f3bf5cf9827.js:1:591014)
    at https://www.appsheet.com/assets/66aa69d7b3241cd0537457156d984eeb70a8f7c16b5f4da6ef6e7f3bf5cf9827.js:1:585353
    at Array.map (<anonymous>)
    at n.value (https://www.appsheet.com/assets/66aa69d7b3241cd0537457156d984eeb70a8f7c16b5f4da6ef6e7f3bf5cf9827.js:1:585306)
    at n.value (https://www.appsheet.com/assets/66aa69d7b3241cd0537457156d984eeb70a8f7c16b5f4da6ef6e7f3bf5cf9827.js:1:582501)
    at n.value (https://www.appsheet.com/assets/66aa69d7b3241cd0537457156d984eeb70a8f7c16b5f4da6ef6e7f3bf5cf9827.js:1:603905)
    at n.value (https://www.appsheet.com/assets/66aa69d7b3241cd0537457156d984eeb70a8f7c16b5f4da6ef6e7f3bf5cf9827.js:1:604354)

 

 

Solved Solved
0 5 103
1 ACCEPTED SOLUTION

I can't find the engineering ticket for this, it's possible support hasn't filed one yet. Please ask them to assign it to me.

With the tools I have and my psychic debugging powers, there is a broken expression somewhere causing this. You have an expression running a set difference operation (the `-` operator) and it's blowing up trying to figure out the base type of one of the operands (i.e. it's a list, but what is it a list of?).

View solution in original post

5 REPLIES 5

Looking into it, thanks very much for the stack trace

 

I can't find the engineering ticket for this, it's possible support hasn't filed one yet. Please ask them to assign it to me.

With the tools I have and my psychic debugging powers, there is a broken expression somewhere causing this. You have an expression running a set difference operation (the `-` operator) and it's blowing up trying to figure out the base type of one of the operands (i.e. it's a list, but what is it a list of?).

Hey Jess! would you please give me some psych1c* powers training? I'd happily pay for it ๐Ÿ˜ƒ

I had one column with a "- LIST()" in its formula. It went like this: 

[Related Refs A][EnumList of Refs B-1] +
[Related Refs A][EnumList of Refs B-2] - LIST()

I removed "- LIST()", replaced it with UNIQUE(), and the problem was solved. 

Thanks much!!

----

* ๐Ÿ˜„๐Ÿ˜„๐Ÿ˜„

Joseph_Seddik_0-1710307682678.png

 

It is very funny that they ban that word. The phrase is from Raymond Chen from when he was able to look at the code but not run the program to reproduce a bug. We should either not allow this at edit time or handle it at runtime, but I'm glad I was able to help 


@infinitejess wrote:

The phrase is from Raymond Chen


Didn't know that, thank you!


@infinitejess wrote:

We should either not allow this at edit time or handle it at runtime, but I'm glad I was able to help


Thanks!

Top Labels in this Space