App no longer uses custom form view when editing existing record

[KingsGuava]

Hi all, we're observing an interesting error in our deployed apps. If a user selects the default "Edit" action, it takes them to a temporary "form" view instead of the customized form view. For now, it seems to only occur with one of the tables in the app. No changes have been made to the app in the past week. Is anyone else running into this behavior? It's exposing users to some columns that they don't need to see when editing a form.

Another interesting aspect of this bug is that if users try to add a new record to the table, it takes them to the correct form view. The error only happens when they try to edit an existing record on a specific table.

[Marc_Dillon]

What all slices are involved here, and what prominence do the form views have?

[frankarv]

This seems to happen even on un-deployed apps

@Marc_Dillon for me it's slices and tables.

Example:

Supposedly the right form view order:

Column 1

Column 2

Column 3...

What the edit view order retrieves:

Column 3

Column 1

Column 2...

[KingsGuava]

After digging into the app a bit more, it seems that a slice was made to limit certain actions that appeared in the dashboard view when the same table was used in multiple dashboard components. For some reason, it looks like the default system views for "detail" and "form"  for the slice weren't created when the slice was created.

Unfortunately, the issue wasn't elevated because we thought that slices would use the "detail" or "form" views of its parent table if one wasn't provided for the slice specifically