Exporting of saved views by module would be an excellent improvement. In general though, view management is a larger and more general pain-point. It would be ideal if in addition to exporting, the platform could provide us with details for each view. For example, saved view 1 is used in action "x" and action "y", and is applied in dashboard "z". This is beneficial because we often have to clean up models with a proliferation of views and actions, mostly old and unused. The only way to do this currently is to export the contents of 'Import Data Sources' into excel, and search the appropriate column for the view of interest. And this must be repeated for every view in the model to ensure a robust clean-up. This is manual and error prone. Having saved view information easily accessible in the platform will make model cleanup and support more efficient and reduce the number of application defects reported internally for our customers by supporting model builders making fewer errors.
... View more
The workarounds are good, but in some cases the additional line items/modules will increase the size more than desired. In the case of large data HUBS where these "counts" are needed for data validation purposes, a function similar to excel "count" would be very useful and help reduce model size and complexity.
... View more