A company uses Microsoft Dataverse rollup fields to calculate insurance exposure and risk profiles for customers. Users report that the system does not update values for the rollup fields when new insurance policies are written. You need to recalculate the value of the rollup fields immediately after a policy is created. What should you do?

Question

Accepted Answer

B. Create a plug-in that uses the update method for the rollup field. Configure a step on the Create A plug-in registered on the `Create` event of the policy entity can programmatically trigger an `Update` operation on the parent customer entity; this action forces the Dataverse rollup field to re-evaluate and update its value immediately.

Answer

A. Create new calculated fields on the customer entity for insurance exposure and risk. Configure Calculated fields are derived from formulas on the same record or related records, but they do not actively force the recalculation of existing rollup fields when new child records are added.

Answer

C. Create new fields on the customer entity for insurance exposure and risk. Write a plug-in that is While a plug-in is the correct approach, this option is too vague and does not specify the critical action of using the `update method for the rollup field` or its parent record.

Answer

D. Create new fields on the customer entity for insurance exposure and risk. Write a workflow Standard workflows do not provide the direct capability to force an immediate recalculation of rollup fields in response to a child record's creation; their capabilities are generally declarative or use limited actions.

A company uses Microsoft Dataverse rollup fields to calculate insurance exposure and risk profiles for customers. Users report that the system does not update values for the rollup fields when new…

Question

Options

How the community answered

Why each option

Community Discussion