Display row numbers in "column order" part of view editor

[Kirk_Masden]

Here’s a simple request. Please display these numbers

in the “column order” section of the view editor like this:

Reason: Virtual columns in tables are displayed in the order they were made. This order may, of course, be different from the order in which the results are displayed in a given view. However, because AppSheet doesn’t provide us with a search function, it can really be hard to find the column that needs editing if you have a lot of virtual columns.

By the way, here’s how columns can multiply:

Because one large table can give birth to multiple slices, each requiring a significant number of columns for either calculation or display, and slices may feed more than one view, a large number of columns can become necessary as an app grows.

It would be ideal if we could have a little link next to each column in the view editor that would take us directly to the column to be edited. I can imagine, however, that that would be difficult to implement. In the meantime, couldn’t we have the numbers to help us locate the appropriate column more quickly?

P.S. This feature request is related to this feature request:

Better search capabilities within the AppSheet editing interface Feature Requests

As AppSheet has grown, it has become possible to develop apps in which columns, actions, and expressions interact in increasingly complex ways. The ability to build more complex apps is great but it can be very difficult to figure out what is connected to what when one returns to an app after some time has passed. We can use our browser’s search function in some contexts to solve such puzzles but the current search function is extremely limited. So, here’s my proposal: Add the capability to …

and to this “tip”:

App Design: Multiple tables vs. Single table + multiple slices Tips & Tricks 💡

One spreadsheet table per “entity” (a set of things in the real world) is the norm in AppSheet: Every entity that you define (Job, Employee, Building) should have its own table (or sheet) within the document that you are connecting to AppSheet. Put more simply, it is often the case that a “view” (UX) will have it’s own table. I think this is good standard practice for beginners but there are potential drawbacks. When, for example, I built a flashcard app with a separate table for each “s…