New Bug Encountered: AppSheet reading the wrong number of table columns from the database

[Harriswe]

I have been seeing errors appearing for formulas that used to work, even though neither they or the underlying table have been updated.

A probable cause of the formula error appears to stem from AppSheet incorrectly reading the table in the MySql database. I.e it reads 6 columns, when there are in fact 21. Hence some of the formulas appear to be referring to fields that do not exist, but they physically do in the database. The first screenshot shows AppSheet thinking there are only 6 columns.

The next screenshot shows the physical table definition.

I have raised the issue with the support team and wonder if anyone else has experienced this issue? At present the issue is one application and not any others.

[Koichi_Tsuji]

Surely silly question to you, but
Regenerateing table is not going to help at all?

[Harriswe]

Hi @tsuji_koichi thank you for your suggestion; unfortunately no. That was my first port-of-call.

The only way I can resolve the issue is to revert to a previous version, where the errors are not occurring. However, having done that while doing an update, sometimes on a different table, the errors start again. Someone on the AppSheet team thinks it relates to the database connection.

But why this app and not another app that uses the same the database?

Puzzling, hence the reason for reaching out to the community to see if this ‘type’ of issue has occurred before.

[Koichi_Tsuji]

Yeah, sounds like the problem is ODBC or something, only Appsheet dev team could solve.