Inconsistent form experience between Desktop Layout and traditional

[Jason_Leffler]

It appears that when clicking a built in "edit" action in a detail view when in desktop layout, that the detail view basically just converts to being editable based on how the fields "editable" definitions are set up.

HOWEVER, the traditional or mobile layouts when clicking edit on a detailed view it goes to the premade (or custom made) "form" view that is attached.

While convenient and clean looking in desktop layout, this is problematic because there is no way to edit the "form" view (edit view) for that detail page when viewing in desktop layout.  

For example, I wish to not have a certain field displayed in the "edit" or "form" view of this detail view, but if I remove it from the prebuilt or custom "form" view that is attached to that detail view, it does not go away.

[Jason_Leffler]

Additional note:  I realized while tinkering that I can use context() to impact the fields in desktop layout when the built in edit action is clicked by referencing the view as the name of the detail view.  So it seems like Desktop layout is basically "turning on" editing, rather than taking you to the connected form

[Steve · Accepted solution]

Here:

[Jason_Leffler]

Thank you so much!  I was looking for something like this, but was looking in the views rather than the action.  Much appreciated!

[Steve]

Yeah, it took me awhile to find it. I knew it was somewhere!