> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/incident-configuration/incident-customization/create-an-incident-field/troubleshoot-incident-fields.md).
# Troubleshoot incident fields
Troubleshoot conflicts with custom incident fields
When trying to download a content update, you may receive the following message:
`Warning: content update has encountered some conflicts`
This occurs when a content update has an incident field with the same name as a custom incident field that already exists in Cortex XSOAR.
To resolve this issue, perform the following steps:
Click **Install Content** to force the update and retain your custom incident field. The content update will install without the system version of the incident field.
Troubleshoot closing a case incident after changing the field type
After deleting a field of type Grid (table) and creating a new field of another type (string, long text, etc.), you may receive the following error when trying to close or update an incident:
`Cannot convert type []interface {} of '[map[] map[]]' to type string, field: sourceip (8902)`
This error occurs with field type changes, if the fields are not compatible types, such as changing the type from long text to boolean or URL to short text. If you create an incident with that field, delete the field, create a new field with the same name but a different type, and then try to close the incident with that field, the error occurs.
For example, create a field of type table/grid and associate it with an incident type. Create an incident with that field, delete that table/grid field, and create a new field with the same name but associate it with a different type (such as short text). When you try to close the incident that has that field, an error may occur.
To resolve this issue, perform the following steps:
1. Go to **Settings & Info** → **Settings** → **Object Setup** → **Incidents** → **Types**.
2. Select the incident type that contains the changed field.
3. Click **Edit Layouts**.
4. Select the tab you want to edit.
5. Add the field you changed to the layout.
6. Save the form.
7. Go to the **Incidents** page and select the incident.
8. Click **Close** if you want to close the incident or **Edit** if you want to edit the incident.
9. In the **Custom Fields** area, reset (delete) the value for the field you changed.
10. Click **Close Incident** or **Update Incident**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/incident-configuration/incident-customization/create-an-incident-field/troubleshoot-incident-fields.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.