> 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/integrator-for-notes/error-messages/new-line-character-appears-as-a-square-box.md).

# New line character appears as a square box

**Description**

A multi-value field or a single value field with carriage returns exported to the corresponding word document which is placed inside a table produces lines that are not separated. Instead of a carriage return, a square box appears in its place.

**Solution**

This is a "known" problem with MS Word application. Apparently, it seems that when the field is placed within a table, MS Word  cannot recognize the new line character.

The trick is to press ENTER after the field (this way, you will have the table with one row and two lines - first one will contain field bookmark and second one will be empty; you can set font to 1, so it would hardly be visible at all).


---

# 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://docs.swingsoftware.com/integrator-for-notes/error-messages/new-line-character-appears-as-a-square-box.md?ask=<question>&goal=<endgoal>
```

`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.