Fix a Missing Resource Custom Field in Project Online
Question details
A resource custom field appears to have been created in Project Online but is unavailable, and its name cannot be reused.

- Product
- Microsoft Project Online and Project Web App
- Device & OS
- not provided
- Scenario
- An administrator is creating an enterprise resource custom field for use in Project and Project Web App.
- Observed behavior
- The field does not appear in Project or Project Web App, while an attempt to create it again reports that the name already exists.
Sign in to Project Web App with permission to manage enterprise custom fields, lookup tables, and queue jobs. Note the field name and any associated lookup table before checking the configuration.
Check Project Web App queue jobs
Use the queue to identify a failed or blocking job that may have prevented the field or its related resources from being created.
In Project Web App, open Settings and select PWA Settings, then select Manage Queue Jobs.
Review recent failed, blocked, or pending jobs around the time you created the field or imported resources. Open a relevant job to inspect its error details.
Use the job details to investigate the reported error. If a retry option is available and appropriate, retry the job after correcting the cause; otherwise, contact your Project Online administrator or Microsoft support.
Return to PWA Settings > Enterprise Custom Fields and Lookup Tables and look for the field before attempting to create it again.

Validate and correct the associated lookup table
Use this approach when the missing resource custom field depends on a lookup table.
Manage project documents and resource lists with WPS Office
WPS Office is a free, lightweight alternative for working with project documents and spreadsheets. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files, though it cannot fix Project Online queue jobs or enterprise custom fields.

Frequently Asked Questions
Why does Project Online say the field name already exists when I can't see it?
The creation process may not have completed successfully even though the name is already in use. Check PWA Settings > Manage Queue Jobs for errors, and inspect Enterprise Custom Fields and Lookup Tables before trying the name again.
Where can I check for failed Project Online jobs?
In Project Web App, open Settings > PWA Settings > Manage Queue Jobs. Look for failed, blocked, or pending jobs near the time of the field creation or resource import.
Can a lookup-table value prevent a custom field from being created?
Yes. A problematic value can cause creation to fail. Open the table under PWA Settings > Enterprise Custom Fields and Lookup Tables and check each value against the table's code mask and separator settings.
Must I remove every period from a lookup table?
No. A period caused the failure in the reported case, but whether it is problematic depends on the lookup table's configuration. Check the code mask, separators, and any queue error before changing values.
What if resources also fail to appear in the Resource Center?
Check Manage Queue Jobs for resource import failures or blocking jobs. Open the relevant job details and investigate the reported error; the missing resources may require separate troubleshooting.




