The domain view a column reads through
How an entity is interpreted in a column, and switching to another domain's view.
How each entity is interpreted
Records are read in your tenant's domains: the domains open to the tenant on Domain & Application Management, plus everything that belongs to no domain. A field scoped to a domain the tenant has closed, or to an application, does not appear here.
When the tenant has an EntityView for an entity in one of its domains, the column reads through it: the view's labels and field order, its hidden fields gone, its required and read-only rules applied when you add or correct a record. The column header then shows the domain's name; hover it to see the view.
Switching
When more than one of the tenant's domains has a view of the same entity, click the domain name in the column header (or choose Domain view in the column menu). Use here switches this column to another domain's view, or to No domain view (the entity's own fields in the tenant's domains); Open beside opens the same entity in a new column with that view, so you can compare two interpretations of the same records side by side. The first domain's view is the default.
Each column keeps its own view for everything done from it: loading more records, adding a record, and the record view with its edits and history. The server checks the choice every time; a view that is not one of the tenant's open domains' views for that entity is not applied, and the header shows the view actually used. A column's view is not saved; the next time you open Explorer, columns start with the default view.
Keep in mind With only one view for an entity there is nothing to switch to, and the Domain view menu says so. Inside an application whose own view reads the entity, the application's view applies and the domain view cannot be switched.
