Saved views versus Custom views for NUX

Options
jwrenne01
jwrenne01 Member, ALL USERS, Partner, Certified Model Builder Posts: 5 Occasional Contributor
in User Experience

Hey Everyone,

 

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.

 

Thanks! 

Tagged:

Comments

  • jwrenne01
    jwrenne01 Member, ALL USERS, Partner, Certified Model Builder Posts: 5 Occasional Contributor

    Thanks Rob!  This certainly kicks things off.  

     

    Custom views:  

    1)  Allows for more colors and and styles for conditional formatting.

     

     

    Saved Views:

    1)  When the same data layout will be used for multiple cards. (Sometimes, typically I still create custom views.)

    2)  Column width needs to be specific. 

     

    Questions for everyone: 

     

    Are there any other cases for when saved views are the better choice? 

    What other inherent functionality can only be utilized through custom views? 

     

    Thanks! 

     

     

     

  • brettnish
    brettnish Member, ALL USERS, Partner, Certified Model Builder Posts: 5 Occasional Contributor

    Something I haven't seen mentioned yet is whether or not ALM is active. If you have to run a sync from DEV to PROD to update any Saved View it may make more sense to recreate them as Custom Views so that you can still update them in the PROD App without needing a sync (imagine if your PROD model only does a sync once a week or less)

Categories