# CASE: multiline\_table

**URL:** <https://community.silverfin.com/t/case-multiline-table/2312>\
**Category:** Cases\
**Tags:** styling, use\_case, string-filters\
**Created:** [June 30, 2022, 1:53pm UTC](https://community.silverfin.com/t/case-multiline-table/2312 "2022-06-30T13:53:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![t0gden](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/t0gden/32/1842_2.png) [@t0gden](https://community.silverfin.com/u/t0gden)\
**Post date:** [June 30, 2022, 1:53pm UTC](https://community.silverfin.com/t/case-multiline-table/2312/1 "2022-06-30T13:53:59Z")

</div>

`multiline_table` is a [string filter](https://developer.silverfin.com/docs/string-filters) that replaces any new line characters `\n` with an HTML line break tag `<br />`. This ensures that text is displayed on new lines as intended.

Be sure to use the `multiline_table` filter when displaying the value of any variable where there is potential for text to be entered across multiple lines.

Let’s take a look at an example of when and how to use the `multiline_table` filter and also how our text would be displayed if we did not use it.

**Example - Displaying a custom text input field**

```auto
**Additional Notes**
{% input custom.text.field as:text %}

{% stripnewlines %}
| example
| output
{% newline %}
|----30%----
|----70%----
{% newline %}
| Custom text field (no filter)
| {{ custom.text.field }}
{% newline %}
| Custom text field (filtered)
| {{ custom.text.field | multiline_table }}
{% newline %}
{% endstripnewlines %}

```

![image (1)](https://canada1.discourse-cdn.com/flex030/uploads/getsilverfin/original/2X/f/fe5f0f08b5bf980a32c6b6dbf669ea0e89c10d5e.png)

As you can see from the example above, without the string filter, the inputted new lines are ignored and the text is displayed on the same line.

By using the `multiline_table` filter our text structure is maintained and is displayed as intended, across multiple lines.

Happy coding!
