Formatting Issues

Fix WebMerge Data Inserting Line Breaks Instead of Paragraph Breaks in Word

Jason MillerJason Miller Oct 28, 2026 869 views

Question details

Ensure data routed from Formstack via WebMerge inserts proper paragraph breaks (^p) instead of manual line breaks (^l) in Word templates to maintain numbered list formatting.

How to Fix WebMerge Inserting Line Breaks Instead of Paragraph Breaks in Word
Product
Microsoft Word / WebMerge
Device & OS
not provided
Scenario
Automating document generation using Formstack and WebMerge to fill out a Word template that contains numbered lists.
Observed behavior
WebMerge inserts manual line breaks (^l) for multiline text data, causing numbered lists to format incorrectly as a single list item rather than continuing to the next number.
Before you start

Ensure you have access to your Formstack data routing settings and WebMerge automation pipeline, as this formatting issue is best resolved at the integration level before the final Word document is generated.

Solution 1Recommended

Use WebMerge Data Formatting Modifiers in the Pipeline

Format the data before the Word document is generated using built-in data formatting options to convert standard text newlines into Word paragraph marks.

The most reliable method is to replace the line breaks during the data transfer process. Attempting to use Word macros or manual Find and Replace after the document is already generated defeats the purpose of automation and can cause file corruption if pipeline arguments conflict.

1
Log into your WebMerge account

Access your Formstack Documents (formerly WebMerge) dashboard and navigate to the specific Document mapping that is causing the issue.

2
Locate the multiline field tag

Find the specific field tag in your mapping that handles the multiline text incoming from Formstack.

3
Apply a text replacement modifier

Update the field tag using Formstack's replacement modifiers to swap basic newlines with paragraph breaks. Check the official WebMerge 'Formatting Your Data' documentation for the exact syntax to map the incoming data as a true paragraph break.

4
Run a test merge

Generate a test document through the pipeline to verify that the numbered list now successfully continues to the next number.

Use WebMerge Data Formatting Modifiers in the Pipeline
Documentation Resource: Consult the official WebMerge/Formstack documentation under 'Formatting Your Data' to ensure you are using the correct regex or modifier syntax for your specific data format.
Free Microsoft Office alternative

Edit and Format Generated Documents Seamlessly with WPS Office

If you frequently deal with automated document generation and need a reliable, lightweight word processor to review or fix formatting issues, WPS Office offers complete compatibility with Microsoft Word documents. It handles complex lists, paragraph marks, and advanced Find and Replace functions effortlessly without the high subscription costs.

  1. 1. Download and Install: Get WPS Office for free from the official website and install it on your device.
  2. 2. Open Generated Documents: Launch WPS Writer and open your automated .docx files without worrying about compatibility loss.
  3. 3. Quickly Adjust Layouts: Use the highly intuitive ribbon interface to find and replace formatting characters or tweak list styles instantly.
Fully compatible with Microsoft Word formats (.docx), ensuring automated templates open flawlessly.Advanced Find and Replace tools seamlessly handle special formatting characters like manual line breaks (^l) and paragraph marks (^p).Lightweight and fast, opening large generated reports instantly.Free to use with a familiar, easy-to-navigate interface.
QA img-9

Frequently Asked Questions

What is the difference between a manual line break and a paragraph break in Word?

A manual line break (inserted via Shift+Enter) moves text to the next line without starting a new paragraph, which keeps the text within the same numbered list item. A paragraph break (inserted via Enter) creates a distinct new paragraph, which prompts a numbered list to continue to the next sequential number.

Why does Formstack text area data break Word numbered lists?

Multiline text fields in web forms often use basic newline characters. When pushed through WebMerge into a Word document without formatting modifiers, these translate into manual line breaks (^l) instead of Word's expected paragraph marks (^p).

Can I automatically fix line breaks using a Word macro after generation?

While you can record a macro to find manual line breaks and replace them with paragraph marks, triggering it securely and automatically every time a document generates from an API is complex and prone to security restrictions. It is highly recommended to fix the data mapping directly in your WebMerge pipeline instead.