Others

How to Troubleshoot Planned Progress Field Errors in Microsoft Project

Elise Williams Oct 15, 2026 869 views

Question details

The user is experiencing calculation errors in the automated Planned Progress custom column in Microsoft Project after uploading the file to SharePoint.

How to Troubleshoot Planned Progress Field Errors in Microsoft Project

Product: Microsoft Project
Device & OS: not provided
Scenario: Tracking project progress automatically using custom fields within a file hosted on a SharePoint folder.
Observed behavior: The custom Planned Progress field, along with related underlying fields like Date1, Number2, and Text10, are displaying errors instead of automatically calculating the expected progress metrics.

Before you start

Verify that your Microsoft Project file is not in a restricted read-only mode in SharePoint and that you have full edit permissions to modify custom field attributes.

Solution 1Recommended

Inspect and Fix Custom Field Formulas

Check the underlying formulas for the Planned Progress field and its dependent fields to ensure no syntax errors or invalid data references exist.

Errors in automated custom fields usually stem from incorrect formula syntax or missing data in reference fields. Because the Planned Progress field relies on Date1, Number2, and Text10, any error in those base fields will cascade into the final progress calculation.

Open Custom Fields

In Microsoft Project, go to the 'Project' tab on the ribbon and click on 'Custom Fields' in the Properties group.

Locate Problematic Fields

Ensure the 'Task' or 'Resource' toggle is selected correctly, then locate the 'Planned Progress', 'Date1', 'Number2', and 'Text10' fields.

Check Formula Syntax

Select the field showing an error and click the 'Formula...' button under the Custom attributes section. Review the formula for any typos, divide-by-zero potentials, or invalid field references, and correct them.

Verify Summary Calculation

Under 'Calculation for task and group summary rows', ensure 'Use formula' is selected so that roll-up summaries calculate correctly instead of displaying errors.

Solution 2

Re-establish Missing SharePoint Dependencies

Fix broken links to external resources or sub-projects that may have disconnected when the file was moved to SharePoint.

Solution 3

Reset Conflicting Filters and Layouts

Clear custom views, groups, or filters that might be corrupting the display of the Planned Progress data.

Free Microsoft Office alternative

Manage Project Data Seamlessly with WPS Office

While WPS Office does not natively replace Microsoft Project, WPS Spreadsheet is a robust, free alternative for tracking project progress, timelines, and budgets. You can easily build automated project trackers using powerful formulas without worrying about complex dependency breaks.

1. Download WPS Office: Download and install the free WPS Office suite from the official website.
2. Open a Project Template: Launch WPS Spreadsheet, go to the homepage, and search for 'Project Management' in the templates library.
3. Track Progress: Use standard Excel-compatible formulas to automatically calculate task progress, eliminating complex external dependency errors.

Completely free, lightweight, and fast to installHighly compatible with Microsoft Excel (.xlsx) formats for easy sharingFamiliar tabbed interface makes setting up project trackers intuitiveBuilt-in spreadsheet templates for Gantt charts and task management

microsoft office alternative - wps office

Frequently Asked Questions

Can moving a Microsoft Project file to SharePoint change its formulas?

No, moving a file to SharePoint does not alter the underlying formulas themselves. However, it can break file paths to external dependencies or resource pools, which causes the existing formulas to fail and display errors.

Why do custom fields like Date1, Number2, and Text10 show #ERROR?

These fields often serve as underlying variables for a master calculation. If they reference missing data, contain invalid formula syntax, or encounter a mathematical impossibility like dividing by zero, the error cascades to any other custom field relying on them.

How do I fix #ERROR on summary tasks in Microsoft Project?

Open the Custom Fields dialog for the affected column. Under the 'Calculation for task and group summary rows' section, ensure that 'Use formula' is selected instead of 'Rollup'. This forces the summary task to calculate progress correctly based on your custom criteria.

Office Quick Solutions