> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.237/help-center-index/faqs/servicenow-faqs/field-readyonly.md).

# Which steps needs to be performed if a specific field is not read only but it is shown as read only

### Description

This behavior is applicable when a field is editable in ServiceNow UI but it is shown as 'Read Only' in <code class="expression">space.vars.OIM</code> in mapping configuration.

### Cause

The reason could be: A field (corresponding to the actual field of the entity) is not created in "Import set table" or it is not mapped in "Transformation map" for the entity which synchronizing is being done.

### Solution

Create/update configuration related to "Import set table" and/or "Transformation map" for the entity that is being synchronized.\
For steps, please refer [Import Set and Transformation map](/v7.237/connectors/servicenow.md#configure-import-set-table-and-transformation-map).

As 'Import set table' and 'Transform map' configuration are a part of [pre-requisites](/v7.237/connectors/servicenow.md#prerequisites) for ServiceNow connector, we would advise you to relook into the pre-requisites and fulfill all of them to avoid such issues in the future.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opshub.com/v7.237/help-center-index/faqs/servicenow-faqs/field-readyonly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.