I have a point dataset, with many of the fields invisible.
I create a selection on that point dataset, and use selection=>create layer from selected features. That works, but now all the fields which had been invisible now become visible. Why? That doesn't seem logical. I didn't want them to display in the old dataset, and it is unlikely that I want them to display in the new subset.
Not a big deal, but more pointing and clicking. I seem to do much pointing and clicking with arcmap. Too much.
and you can delete the fields you don't want from the fieldmap
The difference is that you now have a new dataset with the fields you don't want rather than trying to rely on a view of the original file with the fields hidden
Yes, but the reason to hide fields is to make the user experience better yet keep the possibility of resurrecting some or all of those fields. For example, Business Analyst datasets have several hundred fields. It is tiresome to have to scroll left to right to find those of interest, yet at some future data I might see the need to visit a handful of those fields.
There are many workarounds, yes, but this seems like a poor default behavior.
Dan, I have frequently found your posts most useful, and I thank you for them. This is a pretty small potatoes issue, certainly, but I really think you are being an apologist for a second best ESRI design decision. If I have fields invisible in the original dataset, it is more likely that not that I wish them to rmain invisible in some new dataset created from it by the operation described.
Robert... I am not an apologist by any stretch of the imagination (just ask some of the esri peeps that have been around since 1998)
I just organize my workflow differently than you
I have not expectations for anything, so I plan accordingly.
It mitigates surprises and disappointments