Solved: Avoid conflict when adding new field to published ... - Page 2

Griff · 02-10-2021 06:02 PM

I have an app that is published and being used by several users. In the past when I have made changes to the underlying data I have had instances where the app crashes with the warning that the number of columns don’t match. That turns into a major exercise, especially for Android users, who sometimes end up having to empty the cache, remove appsheet, reinstall appsheet and reopen the app.

I now have to, once again, add a few columns to some of the data. What is the recommended approach to do this and avoid issues?

Steve

Never add new columns between or before existing ones; only add new columns after existing columns.

When removing columns, only blank them, do not delete them.

This may reduce problems, but may not eliminate them.

View solution in original post

Avoid conflict when adding new field to published app