# Support for Newline Character in Template Column Replacements

**URL:** <https://community.glideapps.com/t/support-for-newline-character-in-template-column-replacements/86133>\
**Category:** Feature Requests\
**Created:** [January 25, 2026, 11:19am UTC](https://community.glideapps.com/t/support-for-newline-character-in-template-column-replacements/86133 "2026-01-25T11:19:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexey\_Khrolovich](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/alexey_khrolovich/32/37980_2.png) [@Alexey\_Khrolovich](https://community.glideapps.com/u/Alexey_Khrolovich)\
**Post date:** [January 25, 2026, 11:19am UTC](https://community.glideapps.com/t/support-for-newline-character-in-template-column-replacements/86133/1 "2026-01-25T11:19:51Z")

</div>

Hi Glide Community,

When using the “Replacements” feature in the Template column, there’s no way to target a newline character.

**The Use Case:**  
A very common task is cleaning up multi-line text fields before using them in other constructs. For instance, when building a JSON object, any line breaks in a text value will make the entire JSON invalid. We need an easy way to replace these line breaks with a space.

The most intuitive and user-friendly solution would be to **allow users to physically press the ‘Enter’ key** inside the “Find” input box to create a line break character.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 25, 2026, 11:40am UTC](https://community.glideapps.com/t/support-for-newline-character-in-template-column-replacements/86133/2 "2026-01-25T11:40:59Z")

</div>

> [@Alexey\_Khrolovich](#):
>
> A very common task is cleaning up multi-line text fields before using them in other constructs. For instance, when building a JSON object, any line breaks in a text value will make the entire JSON invalid.

If that’s your only use case, then the recommended approach is to use the native JSON columns (JSON Object/JSON Template). These will automatically deal with any unsupported characters and will always produce valid JSON.

---

<div class="post-metadata">

**Author:** ![Alexey\_Khrolovich](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/alexey_khrolovich/32/37980_2.png) [@Alexey\_Khrolovich](https://community.glideapps.com/u/Alexey_Khrolovich)\
**Post date:** [January 25, 2026, 12:44pm UTC](https://community.glideapps.com/t/support-for-newline-character-in-template-column-replacements/86133/3 "2026-01-25T12:44:16Z")

</div>

thank you!

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [February 1, 2026, 12:59pm UTC](https://community.glideapps.com/t/support-for-newline-character-in-template-column-replacements/86133/5 "2026-02-01T12:59:12Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.