Date: prev next · Thread: first prev next last
November 2017 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=113931

Timur <gtimur@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gtimur@gmail.com
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=10
                   |                            |9118

--- Comment #1 from Timur <gtimur@gmail.com> ---
(In reply to Gabor Kelemen from comment #0)
When creating a Mail Merge document one usually needs to insert Mail merge
fields. This is possible using the Insert - Field - More Fields menu.
I guess you mean Insert - Field - More Fields - Database - Mail merge fields.
However, there is no easy access to this window from the Mail Merge Wizard
or the Mail Merge toolbar, making it hard to discover that one needs to use
this during the document creation workflow, after setting up the data source.
With Bug 109118 in 6.0 I open Data Sources and then just drag fields.
I think it would be helpful to add a .uno:InsertField button to the Mail
Merge toolbar.
If you still find that button useful, please explain when it would be more
useful than Data Sources and drag fields.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.