Understand the model.
Review the change.
Keep the evidence.
A proposed sales change should begin with the definition you actually have.
Here, Northstar Sales is a fictional calculation view, opened from an XML
file.
The workbench parses that source and builds an interactive scenario, with
details and output columns alongside it.
This demonstration uses offline mode.
No database connection or customer data is involved.
Select a node to see its inputs and the mappings that feed its output.
For this example, net amount is calculated from amount using a factor of zero
point nine.
The properties panel exposes the parsed formula.
These are source definitions, not verified database results.
Keep that distinction in mind before accepting any proposed change.
Before changing net amount, open its column lineage.
The upstream path shows the recognized dependencies inside
this loaded view.
Show the path in the graph to connect those relationships
with the model itself.
Highlighted fields and connections provide context.
External definitions and unsupported expressions remain
explicit coverage limits.
Generate SQL for the published output to inspect how the model is translated.
The preview contains a candidate query, including the fictional source object
and calculated expression.
Copy it, or download the SQL for a separate review.
The workbench does not execute that query.
You still need independent validation on your target system.
Analyze View checks the model, then performs an internal
static scan of its generated SQL.
This controlled example contains an identity
projection with an eligible cleanup.
Read the evidence and its scope.
Agree to that application fix, then apply the selected
change.
A finding without an eligible fix remains a review task.
Severity alone never authorizes a rewrite.
The result is a separate XML candidate.
The original source and graph are preserved.
Inspect the exact changes and the optimized XML before
downloading it.
You can also generate SQL from the candidate.
If a selected node was removed, the app falls back to
Output.
Structural checks do not establish runtime equivalence
or better performance.
Now compare the original sales definition with a proposed formula change.
Each side can use an open view or an XML file.
Here, choose the two fictional files.
Run the comparison.
Yellow highlights mark observed structural differences.
Switch to XML to inspect the changed expression directly.
A difference identifies a review point, not a deployment verdict.
Structured reports keep the relationships and coverage
readable in worksheet-style tabs.
Choose a sheet, inspect full cell values, and filter the
rows you need.
Export Excel includes all report tabs and rows.
CSV exports the filtered current sheet.
These are real downloads from the application, ready for
your review process.
When a workflow needs explanation, Help Center opens separately from your
working view.
Search by a feature or a question.
These guides match the active offline application mode.
Connected installations have their own login and catalog guidance.
This recording makes no claim to demonstrate those integrations.
Inspect the source, trace the field, and review the candidate.
Calculation View Workbench.