Interestingly, the field names seem to have changed seemingly for the
better. Whereas before it was inserting things something like
filename.databasename.sheetname.fieldname, now I get "fieldname".
Unfortunately, after running the mailmerge, it seems to have made the
values in the first record (I only have one record currently) a
permanent part of the fields. For example in the fieldname "street
name", it has "Elm St", where it should instead simply have "street
name" making my .odt file useless as a mail merge document, so I'll have
to go through it for the fifth time and change all the fields yet again.
Are you sure they're not still fields? I think after the mailmerge runs,
the fields end up showing data from one of the entries rather than the
field name, but if you re-run mailmerge they do still work as fields.
You can see the field codes rather than the final data by setting Tools
> Options > LibreOffice Writer > View > Field Codes.
This then shows the full databasename.tablename.fieldname code, which
from your previous comment may not be completely ideal, but at least you
can check that they are still fields and not static text. Also, fields
are shown with a grey background, although I'm not sure if that's
another option I've set some time in the past.
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
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