Others

Fix Power Apps Rollup Field Not Showing Calculated Task Costs

Kushani Nimanthika Sep 28, 2026 869 views

Question details

The user needs to aggregate calculated task costs into a Project Cost rollup field, but the calculated field is missing from the column selection.

How to Fix Power Apps Rollup Field Not Showing Calculated Task Costs

Product: Power Apps / Dataverse
Device & OS: not provided
Scenario: Creating a Project Cost or Project Budget rollup field to sum up the costs of related Project Task records.
Observed behavior: The calculated Task Cost field is not available to be selected as the source column for the Dataverse rollup field.

Before you start

Verify that your Project and Project Task entities have a valid one-to-many (1:N) relationship configured in Dataverse and that the calculated task field functions correctly on its own.

Solution 1Recommended

Use Alternative Calculation Methods or Seek Community Support

Dataverse restricts rollup fields from referencing calculated fields that use data from related tables. You must use Power Automate, plugins, or consult experts for an alternative.

In Power Apps and Dataverse, a rollup field cannot aggregate a calculated field if that calculated field references columns from another related table. Because this is a systemic limitation within the Microsoft Power Platform, native rollup configurations cannot resolve this.

Microsoft advises handling these complex cross-entity calculations through external logic, automation flows, or by reaching out to the Power Platform Community for advanced, verified workarounds.

Consult the Power Platform Community

Navigate to the official Microsoft Power Platform Community forums and post your specific entity relationship structure to seek specialized advice from Dataverse experts.

Use Power Automate Flows

Instead of a native rollup field, create a Power Automate flow triggered when a Project Task is created, updated, or deleted. Set the flow to sum the task costs and update a standard currency field on the parent Project record.

Implement Dataverse Plugins

For enterprise environments, a custom C# plugin can be written and registered on the Project Task entity to dynamically calculate and update the parent rollup values in real time.

Use Alternative Calculation Methods or Seek Community Support

Dataverse System Limitation: Rollup fields can only aggregate calculated fields if the calculated field's logic does not cross over to other entities. This is intended to prevent circular references and performance degradation.

Free Microsoft Office alternative

Manage Project Budgets Easily with WPS Office

If Dataverse and Power Apps constraints are making project tracking too complex, consider using WPS Spreadsheets for a free, lightweight, and highly customizable project budget tracker that requires no database administration.

1. Download WPS Office: Install WPS Office for free and open the WPS Spreadsheets application.
2. Set Up Your Project Tracker: Create one sheet for 'Projects' and another for 'Tasks', ensuring you include columns for project IDs and individual task costs.
3. Use Native Formulas: Apply the SUMIF or SUMIFS function in the Projects sheet to instantly roll up the task costs dynamically.

Seamless compatibility with Microsoft Excel (.xlsx) formatsEffortlessly calculate complex project costs using SUMIFS and custom formulas without systemic limitationsFree, lightweight, and features a familiar user interface for rapid adoptionNo complex Dataverse entity relationship configurations required

microsoft office alternative - wps office

Frequently Asked Questions

Why is my calculated field not showing in the Dataverse rollup field selection?

Dataverse restricts rollup fields from using calculated fields that rely on data from other related tables. It will only display calculated fields that exclusively use data from the same entity.

Can I force a Dataverse rollup field to update immediately?

Native rollup fields calculate asynchronously via a system job every 12 hours. You can manually trigger a recalculation by hovering over the field on a model-driven app form and clicking the recalculate calculator icon.

Are there limits to the number of rollup fields per entity in Power Apps?

Yes, Microsoft Dataverse allows a maximum of 10 rollup fields per entity and up to 100 per environment to maintain system performance.

Office Quick Solutions