> 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.206/help-center-index/faqs/servicenow-faqs/link-type-not-available.md).

# Which steps needs to be performed if link types are not visible in mapping for ServiceNow?

### Description

This behavior is applicable when Link type is visible in ServiceNow UI, but you are not able to see it in the Issue relationship section of Mapping.

### Cause

The probable reason could be: A field (corresponding to the link field of the entity) is not created in "Import set table" or not mapped in the "Transformation map" setting for the entity that you are synchronizing.

### Solution

Create/update configuration related to "Import set table" and/or "Transformation map" setting for the link field of the entity that you are synchronizing. For steps, please refer [Configure reference type fields](/v7.206/connectors/servicenow.md#configure-reference-type-fields).

As 'Import set table' and 'Transform map' configuration are a part of [pre-requisites](/v7.206/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.206/help-center-index/faqs/servicenow-faqs/link-type-not-available.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.