I created a google spreadsheet and downloaded it as a CSV file.
I used that as the source of my mailmerge data (presumably using "base" is the only way to use the
CSV file, so that's what I did).
I used an existing MS Word file sent to me by a colleague, as my starting document, opened in
I then entered various Fields from this CSV file (now converted to a "base" file by the mail merge
wizard) into my Writer document for purposes of mail merge. The end result mail merge post processed
document has the field names, no values. The original document with the fields, does not act as if it has
fields - in other words, it's just plain text, not the fields I inserted.
Example: I inserted "Sellers Aggregate1.Sheet1.Owner's Street Address" (a real field) as a field
into the doc, and instead of acting like a field, it acts like normal text. I thought perhaps the spaces,
periods, apostrophes and/or the length of the field name are causing the problem, but then I realized I did
have one field that did not have any of those things, just a simple one word field (other than the additional
things added by the mail merge/database mechanism itself).
This is a critical problem for me.
Thank you in advance
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
- [libreoffice-users] Problems with mail merge · A
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy