While i cannot talk on anaplan stance, but our experience with NUX in recent projects have been exactly what you are suggesting and we are building now with these guidelines in mind : Anything related to presentations (reportings, dashboards or inputs) that can be technically set in NUX is done there instead of models. That includes layouts for dashboards (using filters, pivot...). It is derived from old 3-tier architectures (data / calculations or business logic / presentation) where NUX = presentation layer. Obviously some components still require to be set in models : - Import formats with saved views are still a necessity unfortunately - some tricky lines or column filters when using line items in columns (hope this will be solved as a future ux enhancement) also require a saved view - advanced and shared filters need their own line item to be built in the model itself to be consumed then in NUX Maybe others have different experience and practices, but these above kind of naturally came into motion while we were into projects
... View more
