I am extremely confused about how Appsheet choose between a system generated view of the table or the slice of the table and when does it switch back to automatic selected columns or not.
I have created slices as recommended, but the outcome was an insane chaos of what system view is picked in what situation (add, edit, details, reference). To make it even more confusing, Appsheet sometimes decide to switch the selected columns back to automatic. So that at the end it takes ages to get the views right.
However, this are examples of the actual situation I have now:
By whom? I don’t recognize the convention you’re using.
Views chosen are determined in a variety of ways.
If a user navigates to a view, such as by choosing a navigation element along the bottom of the screen or from the main menu, the view and data are explicit.
If the user clicks on a Ref column value, the default action will navigate to the _Detail view for a row of the table or slice defined for that Ref column value.
If the user clicks on an entry in an inline list (table, deck, chart, card, etc.), the user will go to the _Detail view of the table or slice for that List column.
System views are generated for all tables according to the table’s Are updates allowed? settings. All tables get a _Detail view. If the table allows adds or updates, or the setting is configured with an expression, it also gets a _Form view. If the table is referenced by any List-type columns, it will also be given an _Inline view.
System views for slices are a hot mess. If the slice is used explicitly by any aggregate view (table, deck, chart, card, etc.), a _Detail view is created, and a _Form view if the slice allows adds or updates. If the slice is referenced by any List-type column, it’s given an _Inline view.
Slices attached solely to Enum or EnumList columns do not get system-generated views.
All of this makes my head hurt. What other cases are you seeing?
