Skip to main content
A good view starts with a clear question. Decide what the audience needs to see before you save filters or layout choices.

​
Start from the right source

Create the view on the model or database that already contains the content you need.
  • Use a model view when the question depends on planning logic, scenarios, dimensions, or time-aware outputs.
  • Use a database view when the question depends on source records or operational detail.

​
Save the configuration that matters

A view can save choices such as:
  • filters
  • sort order
  • grouping
  • visible content
  • time or scenario context where the source supports it
The exact options depend on whether the view comes from a model or a database.

​
Name the view for reuse

Name the view after the workflow, audience, or business question it supports. That makes it easier to reuse on boards, in reviews, and in sharing flows.

​
Keep setup separate from source design

If a view needs too many rules to make sense, first check whether the model structure or database structure needs cleanup.