> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/seascape-for-notes/faq/how-to-create-custom-title-and-nd-metadata-fields-in-sharepoint.md).
# How to Create Custom Title and ND Metadata Fields in SharePoint
Follow these steps to create a custom Title and ND metadata fields for a SharePoint export.
1. Start a new SharePoint export as you normally would. During the export setup, create a **new custom metadata field**. You can create two or more Notes fields if required.
2. **Run the export.**
\
When the export starts, the new custom field will be generated and saved in the output XML files alongside the standard metadata fields. After the export is complete, locate the db-**analysis.json file** in the **\db** subfolder of your selected destination folder. Right-click the file and open it in a text editor.
3. **Update the custom field's weight.**
\
In **db-analysis.json**, locate the new custom field you created during the export setup. The field must be a String. Change its **weight** value to a very high number, such as **10000**, and save the file.
4. **Upload the export to SharePoint.**
\
Once the **db-analysis.json** file has been updated and saved, proceed with uploading the files and metadata to SharePoint using the normal procedure.
Once the data has been uploaded, your new custom metadata will be used for the **Title** and **ND columns** in SharePoint.
---
# 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.swingsoftware.com/seascape-for-notes/faq/how-to-create-custom-title-and-nd-metadata-fields-in-sharepoint.md?ask=&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.
