I have been attempting to migrate the back end of my app from Google Sheets to the new database feature while performing some structural updates as well. I want to stay on the same deployed app, so I cloned the app to generate the database and perform the frontend changes. I then went through the tables of my deployed app and backed them up to a new database and switched them to the relevant database table. However, this generated the error:
"The given key was not present in the dictionary."
I found that the way appsheet handles key values is different with databases, and requires the usage of automatically generated row IDs. Fine.
So I cloned my app with a database to perform the frontend changes. The idea was to keep the legacy app running and then upgrade it with the clone. I would then clone the live data into a database to generate the row ID, and then point the upgraded app to the generated database with the live data.
However, I was testing this out with my cloned app, and I found something disturbing: Switching between the original database and an IDENTICALLY STRUCTURED database generates the same error. What's more: I CAN'T SWITCH BACK! Even when I point the table to the original database, the error persists.
Obviously, I'm hesitant now to switch to databases as it looks like any monkeying about with data sources has the potential to permanently break the app.
LinkedIn
Twitter
