In a comma-delimited Data Merge source, an unprotected comma inside a person's display name can be interpreted as a field separator. Quote that complete field correctly, then reload the source and preview the record. Moving text boxes around will not repair data that has already been split into the wrong fields.
Distinguish data structure from layout
Suppose a fictional card has ID, Name and Message fields. A name formatted as surname followed by a comma and given name contains punctuation that also separates CSV columns. Check the plain-text source as well as the spreadsheet view: the sheet can look correct while its export is unsuitable for the receiving workflow.
Adobe documents quoted fields for embedded commas and support for UTF-8 CSV. The source should preserve complete field values before the template places them. Adobe: Data source files.
Start with a harmless three-record fixture
This original fixture uses fictional display names and contains no real customer information. It is a proposed test input, not a completed merge result:
- Header:
ID,Name,Message - Comma case:
case-a,"Chen, Lin","Welcome, friend." - Quote case:
case-b,Ana,"A ""bright"" day" - Chinese case:
case-c,小禾,欢迎来到花园
Straight double quotes surround a field containing a comma. A literal double quote inside a quoted field is doubled. For the commonly documented CSV escaping convention, see RFC 4180. Keep this fixture single-line per record; multiline handling is outside this test.
Save with a known encoding and review the actual exported text. If the editor silently replaces straight quotation marks with decorative marks, correct the data export rather than imitating the visual appearance of the sample.
A separate correct three-record CSV fixture and deliberately broken comparison are available to download. These original files demonstrate parsing inputs using fictional records; they are not InDesign test results. Keep the broken file out of production.
Preview difficult records before the whole batch
Load the source into the intended external Data Merge template. Check each fixture record in the preview. Name must remain one complete value, Message must not contain a fragment of Name, and the Chinese value must remain intact. Then make a small merged document and inspect actual text, not only placeholders.
Use this review note: source row ID; expected Name; expected Message; observed Name; observed Message; pass or fail. Keeping an explicit ID makes it possible to identify a damaged record without relying on its current row number.
If you correct the source, update or reload it before generating the final batch. A repaired CSV on disk does not prove that the application is using it.
Acceptance and production boundaries
Pass when every fixture value survives as the intended field, then review actual recipient records under your normal access controls. Fail on any split name, shifted message, damaged character or stale source preview. After structural correction, check long values for overset separately; correct columns do not guarantee enough layout space.
Imagild can provide a shared illustration for the card design. CSV preparation, personal-data handling and Data Merge belong to external tools. Do not place real mailing lists or recipient details in image prompts simply to produce the decorative artwork.