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

• ACreate new fields on the customer entity for insurance exposure and risk. Write a workflow
• BCreate new calculated fields on the customer entity for insurance exposure and risk. Configure
• CChange the frequency of the Calculate Rollup Field recurring job from every hour to every five
• DCreate new fields on the customer entity for insurance exposure and risk. Write a plug-in that is

• A
  13% (3)
• B
  4% (1)
• C
  8% (2)
• D
  75% (18)

Explanation

Dataverse rollup fields are recalculated asynchronously on a scheduled basis (default: every hour) via the 'Calculate Rollup Field' system job. They do not recalculate in real time on record creation. To trigger an immediate recalculation after a new insurance policy is created, you must write a plug-in registered on the Create message of the policy table that programmatically calls the CalculateRollupField action. Option C (changing job frequency to every 5 minutes) reduces lag but does not provide immediate recalculation. Options A and B describe calculated fields, not rollup fields - calculated fields evaluate on retrieve, but cannot perform aggregations across related records the way rollup fields do.

No community discussion yet for this question.