Calculating Derived Sales Values Without Storing Data in Dataverse
Short answer
D Create a calculated column in Dataverse that evaluates an expression over numeric columns in the same row, computing and returning the result at query time without storing it in the table data.
Question
The company requires the following functionality:
Evaluate an expression by using numerical columns in the same row.
Calculate the result dynamically when accessed.
Ensure the result is NOT stored as part of the table data.
The solution must minimize use of custom code.
You need to configure the app.
What should you do?
Key Takeaways
The question tests the difference between computed-on-access and computed-on-write: only a Dataverse calculated column evaluates at query time without persisting the result.
This Dataverse question tests how to derive row-level numeric values that are computed on access rather than persisted. A calculated column (D) evaluates the expression at query time using same-row columns, storing nothing, whereas business rules, JavaScript and dataflows all persist results or require custom code.
Common mistake: Choosing A, a business rule to populate the value, because it looks like a low-code option — but business rules write the result into the row on save, so the value is stored and only refreshes on save rather than being computed dynamically when accessed.
Expert Analysis
The mechanism: on-access evaluation vs. stored values. Dataverse offers three ways to derive values: rollup/calculated (formula) columns, business rules (or classic workflows) that write a column, and client-side JavaScript. Only one of these computes at read time without persisting the result.
Trace the read path. When an app, flow or lookup retrieves a sales row, Dataverse returns ordinary stored columns directly from the table pages. A calculated column is different: it has no stored value in the row image. Instead, Dataverse evaluates the column's expression at query time, reading only other columns within the same row, and returns the result in the response. Nothing is written to table storage, so there is no update storm, no audit noise and no reconciliation between stored and source values. That is exactly what the requirement "calculate the result dynamically when accessed" and "NOT stored as part of the table data" describes.
Why the expression scope matters. Calculated columns are restricted to columns on the same row (plus related-table lookups in limited form) and support arithmetic and basic functions over numeric Dataverse columns. The scenario explicitly says "using numerical columns in the same row", which is the signature constraint of a calculated column — a strong signal that this is the intended feature. Because it is configured declaratively in the maker portal, it also satisfies "minimize use of custom code."
Why the others fail. A. Business rule: a business rule that populates a value performs an on-save write; the result lands in the row as stored data, so it violates the "not stored" requirement and only refreshes on save, not on access. B. JavaScript: a script runs in the form context and is custom code the requirement forbids; it also only fires in the client UI, not for API or background reads. C. Dataflow: a dataflow transforms and loads data into a destination (e.g., Dataverse or fabric tables), persisting the output — the opposite of a derived, unstored value.
Verdict: D is the only option that computes on access, stays within a single row, persists nothing and avoids custom code.
Exam Strategy
On Dataverse design questions, sort options by where the value lives. The stem's phrases — "dynamically when accessed" and "NOT stored" — point to a query-time computation, which in Dataverse means a calculated (formula) column. Eliminate anything that writes on save (business rules, classic workflows, plug-ins), anything client-side (JavaScript), and anything that loads results into a destination (dataflows, imports). If the stem also says "same row" and "minimize custom code," the calculated column is the intended answer.
Frequently Asked Questions
How does a Dataverse calculated column differ from a rollup column?
Why not use a business rule or JavaScript to derive the value?
Can calculated columns be used in filters and aggregations?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
exam_upskill 👍 1 Answered DD. Create a calculated column.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.