If your generated Google Doc or PDF still shows placeholders, has blank fields, or pulls the wrong row values, fix the template and sheet mapping before running another batch.
When Google Docs merge fields do not replace from Google Sheets, the problem is usually a mismatch between the template placeholder and the selected sheet column, a blank source value, a renamed header, the wrong template file, or output generated before the latest mapping was saved.
Make sure each placeholder is plain text and has the exact name you expect.
Check whether row 1 headers were renamed, duplicated, hidden, or moved.
Run preflight and generate one file from a row that has complete test data.
Spaces, punctuation, capitalization, and braces can matter. If the template uses {{FirstName}} but the mapping expects First Name, confirm the mapping instead of assuming the text will normalize itself.
If a Sheets column was renamed after the merge workflow was configured, open the mapping again and reconnect that field before generating output.
A blank output field can be correct if the source row is blank. Test with a row where required values are visible and easy to verify.
Teams often have multiple draft templates. Confirm the selected Google Docs file is the current version and contains the placeholders you are checking.
If you changed the template or mapping, generate a fresh one-row test. Older files will not update themselves after a mapping fix.
If a placeholder was copied from another source, retype it directly in Google Docs as plain text. Broken hidden formatting can make a field hard to detect.
DocForge is built for template-based document generation from Google Sheets rows. Use the add-on when you want a repeatable workflow with field mapping, preflight checks, and one-file testing before a full batch.
The working fields probably have valid mappings and source values. Recheck the unresolved fields for spelling, renamed headers, blank row data, or copied placeholder formatting.
That usually means the field was found, but the selected row did not have a value for that mapped column. Test with a row that contains obvious sample values.
Exact names are easier to audit, but a field mapping step can still connect different names. The important part is confirming the current mapping before generation.
Generated files are snapshots. After changing the template or mapping, generate a new one-row output and replace the old file if needed.
Install DocForge when spreadsheet rows need to become Google Docs or PDFs through a repeatable template workflow with a safer first-run check.