'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Troubleshoot Uneditable Custom Fields in Microsoft Project Server
Question details
Users are unable to edit custom fields in Microsoft Project Server, finding them stuck in a read-only state.
- Product
- Microsoft Project Server
- Device & OS
- not provided
- Scenario
- Attempting to modify data within an enterprise custom field using Project Web App (PWA) or Project Professional.
- Observed behavior
- The custom field appears greyed out or read-only, preventing the user from updating the project information.
Verify that you have the necessary administrative or project manager permissions in Project Server to modify enterprise custom fields and project data.
Isolate and Fix Field Configuration Issues
Check if the read-only status is caused by internal formulas, active workflows, or enterprise field settings.
In Microsoft Project Server, enterprise custom fields can be locked down automatically by several system configurations. It is crucial to determine if the field is designed to be read-only before attempting to change permissions.
Navigate to PWA Settings > Enterprise Custom Fields and Lookup Tables. If the custom field is calculated using an internal formula, it will naturally be read-only for users and cannot be manually edited.
Check if the project is currently locked by a workflow stage. In Project Server, workflows can enforce read-only states on specific fields during approval phases. You may need to advance the workflow to unlock the field.
Within the Enterprise Custom Fields settings, ensure the field is not restricted to a specific department that excludes the current user or the specific project.
Perform Permission and Scope Diagnostic Testing
Determine if the issue is user-specific, client-specific, or affects all custom fields by running targeted tests.
Manage Projects Easily with WPS Office
While Microsoft Project Server handles complex enterprise workflows, it can be heavy and difficult to configure for everyday tasks. For straightforward project tracking, task management, and team collaboration, WPS Office offers a free, lightweight, and highly compatible alternative. Enjoy a familiar UI, seamless migration, and powerful spreadsheet tools without the steep learning curve.
Frequently Asked Questions
Why are my Microsoft Project Server custom fields greyed out?
Custom fields can be greyed out if they are calculated by a formula, controlled by an active workflow step, restricted to a different department, or if you lack the necessary 'Edit Project' permissions.
Can I force a read-only custom field to become editable?
You can only make it editable by removing the system restrictions causing the read-only state. An administrator must check the enterprise custom field settings in PWA to remove formulas, workflow locks, or department restrictions.
Does this issue happen in both Project Web App (PWA) and Project Professional?
It depends on the root cause. Sometimes a field is editable in Project Professional but read-only in PWA due to web view configurations or synchronization errors. Testing the field in both platforms helps isolate the underlying cause.
