sharepoint view

gbritton - Calculated columns do persist in the underlying list as a column with a value. They are "hidden" from forms by default in SharePoint.

I am very familiar with all of the various customization options for SharePoint Views. The link that you sent doesn't even cover half of what is possible just in tweaking the default view settings. I think that the underlying theme here is that the vast majority of those list options are user experience things and there are so many of them that not all of them would translate to a data ingest process. SQL views by contrast are very limited in what they can do and they essentially come out as a table. Not so with SharePoint, views can look and behave radically differently. Thus, I can see how it becomes problematic trying to support all of those different UI switches in SharePoint views. I'd submit it to Ideas. I think it has merit as something explore.

One note, Lookup fields can be tricky, they store the ID of the item from the other list and if you display other related fields from the lookup list, those are NOT persisted in the SharePoint list, so if you want them, you have to pull in the other list as well and relate them.