> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/administration/additional-troubleshooting/when-i-open-the-template-editor-i-receive-an-attempt-to-de-reference-a-null-object-error.md).

# When I Open the Template Editor I Receive an Attempt to De-Reference a Null Object Error

This error can occur for multiple reasons.

{% stepper %}
{% step %}

### The template’s *Related To Type* object is missing as a picklist option

The template’s *Related To Type* object does not exist as a *Related To Type* picklist option in this org (this usually occurs when templates are imported from other orgs). Add the *Related To Type* object as a *Related To Type* picklist option.
{% endstep %}

{% step %}

### Incorrectly configured lookup field on the S-Doc Relationship object

There is an incorrectly configured lookup field to the *Related To Type* object on the S-Doc Relationship object. Ensure that you have [**correctly configured**](https://www.sdocs.com/resources/documentation/configuring-s-docs-with-custom-objects-salesforce-lightning/#lookupfield) a Lookup field to the template’s Related To Type object on the S-Doc relationship object.
{% endstep %}
{% endstepper %}


---

# 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://help.sdocs.com/sdocs/administration/additional-troubleshooting/when-i-open-the-template-editor-i-receive-an-attempt-to-de-reference-a-null-object-error.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.