Skip to main content
Views are often the easiest place to compare outputs because they let you narrow the data before you ask for a variance.

​
Start with model views

Model views are usually the best place for comparisons such as:
  • scenario versus scenario
  • actual versus forecast
  • current period versus prior period
  • one dimension slice versus another

​
Use database views only when the slice is clear

A database view can still support comparison when the structure already gives you a clean slice to review, such as one category versus another or one filtered record set versus another. Do not assume a database view supports model-style scenario comparison.

​
Keep the context stable

Compare one business question at a time. Lock the right filters, grouping, and time context before you interpret the result.

​
Check the source before you debug

If a comparison looks wrong, confirm the active scenario, Time aggregation, Time rollups, and filters before you assume the formula or data is incorrect.