Yesterday, I noticed a strange behavior with a view I just changed. My client requested to see only base currency fields in the views of opportunity because it was confusing. After the change, all of those were blank. After a quick search, I stumbled upon this article:
https://crmtipoftheday.com/540/blank-base-currency-fields/
Surprised by this new “undocumented feature”, I took upon myself to find a better solution than adding a normal currency field at the far end of the view.
Knowing there was no way to simply hide the column through the configuration, I tried to change the size of the unwanted column to zero, by modifying an extracted solution, which worked like a charm.
The next step was to make sure the change would not crash the view configuration window nor undo itself at the next change. Again, my test was successful. The column appeared to take the maximum size, and adding or removing a column left it hidden.
Note: If you add the hidden column in between others, all you’ll see is an extra separator. If it’s the last column you won’t even see it.
Bonus: I tried another thing. I saw that in the solution’s view definition, there was a part for the layout (LayoutXML) and one for the data (FetchXML). So, I removed the column from the layout, kept the fetch as is and uploaded. It worked, but after the next view modification, I lost the fix because the Layout was rebuilt completely.