As a best practice I create custom views when building in the NUX. I have plenty of colleagues that still prefer making saved views and bringing those into the NUX. Their reasoning is more based on comfortability than best practices. Wanted to ask the community on where people stand on best practices for the NUX? Are there scenarios that anyone has come across that custom views cannot handle but saved views will and what are they?
I would love to create a cheat sheet as to why or when it is appropriate to use saved views versus custom for dashboarding in the NUX. Any help or thoughts would very much be appreciated.
1) When the same data layout will be used for multiple cards. (Sometimes, typically I still create custom views.)
@jwrenne01actually you can use save the card as template in new UX if you want to duplicate the layout. Also this alows you to modify the saved template if let's say you want to select another line item in page selector in this copy. This eventually can save you even more time comparing to using saved view.
@KirillKuznetsov It is true: custom views in NUX can be saved as card templates..However, if you need to change the layout (add columns, etc...) you need to modify the card template and republish in all pages.
If saved views are used, you can change the saved view in the module and all the pages where the saved view was used are automatically updated without needed to republish.
However, because of the fewer functionalities present on the published saved views, I also mostly use the NUX custom views. 🙂
You are right, saved views will help you in cases when you need exact views on various Pages. But Templates can be used in cases when you need to change just a little bit in the template and save some build time instead of creating a card from scratch.