Exclude empty fields from public/private saved views

Joe Cerep 1 year ago in Productivity Management updated by Eric Teitsma 1 year ago 1

It would be great if there were an option to exclude empty fields in a saved view. An example of where this would be a major benefit:

A key part of one of our processes is the availability of data for up to 10 channels. Requests can include any combination of Email, Direct Mail, Browser Notification, Digital, SMS ect. The saved public view we set up for this process has to include all 10 of the Expected Availability for _____ EAs, even though most of them are empty for a specific request. If we were able to exclude empty fields when the view is populated, it would only display relevant fields and would be a much more user-friendly experience.


I understand your specific use case here but I struggle with the implementation of this.  Views are applied to list pages which will have a list of 50 or 100 records usually so the only way we could hide the field is if every record in the current list was empty right?  If you have 50 records and 48 are blank but 2 have a value we still have to show the value.  As a user I would find it odd that sometimes when I open a view there are more columns and other times some columns are missing.  A view is a saved configuration so as a user I would not expect it to change.  If I have consciously selected columns to display I expect them to be there.  This does not really follow UX standards or guidelines.

Also, there will be times when a user will want to know the field is empty right?