Configuring Non-Persisted Derived Values in Dataverse
Short answer
A Create a formula column to dynamically evaluate expressions without storing the result in Dataverse.
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 trap is confusing stored derived values (Business Rules/Workflows) with non-persisted calculations (Formula Columns).
This question tests knowledge of Dataverse derived values, specifically how to create dynamic calculations that are not stored in the database.
Common mistake: Candidates often choose Business Rules because they are common for populating fields, but Business Rules store the value, violating the 'NOT stored' constraint.
Expert Analysis
The question requires a solution that evaluates an expression using numerical columns within the same row, calculates the result dynamically upon access, and ensures the result is not stored in the table data. This specific behavior defines a Formula Column in Microsoft Dataverse.
- Option A (Create a formula column): Correct. Formula columns are computed on-the-fly when queried and do not persist data in the database, satisfying the "minimize custom code" constraint while meeting all functional requirements.
- Option B (Use a real-time workflow): Incorrect. Workflows execute actions but typically require saving data or triggering events; they do not provide a dynamic, non-persisted view of calculated values directly in the record structure without storage.
- Option C (Use a business rule): Incorrect. Business rules populate fields by setting their values, which means the result would be stored as part of the table data, violating the requirement.
- Option D (Use a plugin): Incorrect. While plugins can calculate values, they involve custom code execution and usually result in updating a field's value (storing it), which contradicts the "minimize custom code" and "NOT stored" constraints.
The key differentiator is the persistence model: only Formula Columns provide dynamic calculation without storing the result.
Official Reference
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/formula-column
This link opens the official vendor documentation in a new tab.
Exam Strategy
When questions specify 'dynamically when accessed' and 'NOT stored', immediately eliminate any option that implies writing to the database (like Business Rules, Workflows, or Plugins). Look for features designed for read-only computation like Formula Columns.
Frequently Asked Questions
What is the difference between a Formula Column and a Business Rule?
Can I use a Plugin to avoid storing data?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
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
-
ah2006 👍 1 Answered AFormula column
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.