---
title: "Customfield_XYZ cannot be set."
canonical: "https://support.appfire.com/space/DLP/298419792/Customfield_XYZ%20cannot%20be%20set."
format: markdown
---
**Table of contents**
> Macro (toc)
When using the Cloud version of our App, you may encounter the following error:
*Project Key XXX - customfield_XXXXX: Field 'customfield_XXXXX' cannot be set. It is not on the appropriate screen, or unknown. *
> ℹ️ **To resolve this problem, you must have Jira administrator permissions.**
The App is trying to use an issue field and fails because the field is missing from a Jira project screen scheme.
In the example above, the problem concerns:
- a Jira project with a key: **DP0**
- a field:** customfield_10015**
## Classic Projects
### Find the Field Name Missing from the Screen Scheme
1. BigGantt and BigPicture may use issue custom fields. Those custom fields are configurable under **Apps > Manage your apps. **
2. From the list on the left, access **BigPicture/ BigGantt Configuration. **
3. A warning will appear. Click** Cancel **to access the App configuration.
4. Go to the** General > Fields **tab.
5. If the project in question uses **custom mapping settings**, check them specifically. As specified in the warning message, the Jira project in question has the following Key: **DP0.**
6. Switch to the **"Custom mapping"** section. Click on the project name or the **Edit **button to see the settings. The custom field ID will help you quickly locate the field in question. In this case, because **customfield_10015** was listed in the warning message, we know the **Start date **is** **the field missing from the screen scheme**.**
### **Use the Project Key to Find the Project**
1. Click **Projects **> **View all projects**.
2. Enter **DP0 **in the search box.
3. Open the project by clicking on its name.
### Find the Screen Scheme Associated with the Project
1. Go to the **Project settings** page.
2. Select **Screens **from the list on the left.
### Find the Fields Associated with the Screen
Update the Issue Type Screen Scheme(s)
1. Click the **edit **button on the right.
2. Click the name of the screen.
3. You will see the list of fields associated with this screen scheme.
4. Add the missing field (**Start date**) to the screen scheme.
> ✅ Once all the issues have been addressed, clear the log by clicking the 'Clear log' button within the 'Program warnings' dialog. Even if issues have been fixed, the dialog box won't disappear until the log has been cleared.
---
## Team-managed Jira projects
Activate the toggle switch on the **BigPicture configuration > General > Fields** page. The App will run without problems, even though the fields have not been added to the issue types.
> ℹ️ Keep in mind that the use of team-managed Jira projects is not recommended.
Keep in mind more than one field can be causing an issue.
### Check the Technical Configuration of the App
1. BigGantt and BigPicture may use issue custom fields. Those custom fields are configurable under **Apps > Manage your apps. **
2. From the list on the left, access **BigPicture/ BigGantt Configuration. **
3. A warning will appear. Click** Cancel **to access the App configuration.
4. Go to the** General > Fields **tab.
5. If the project in question uses **custom mapping settings**, check them specifically. As specified in the warning message, the Jira project in question has the following Key: **NXTGN2022.**
6. Switch to the **"Custom mapping"** section. Click on the project name or the** Edit **button to see the settings. Scroll down to find the **toggle switch**. Make sure to hit **Save.**
> ✅ Once all the issues have been addressed, clear the log by clicking the 'Clear log' button within the 'Program warnings' dialog. Even if issues have been fixed, the dialog box won't disappear until the log has been cleared.
