Problem description: Mailmerging is not possible in Draw like it is in Writer. In Writer you can add "other" fields from a Database, but not in Draw. This would allow functionality of using Draw in more ways, perhaps making it more comparable toward MS Publisher. Steps to reproduce: 1. Open Draw 2. Navigate to Insert on menubar 3. Click Fields Current behavior: Only standard fields are available Expected behavior: "Other..." fields available Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.2; rv:15.0) Gecko/20100101 Firefox/15.0
Adding self to CC if not already on
*** Bug 93397 has been marked as a duplicate of this bug. ***
*** Bug 78155 has been marked as a duplicate of this bug. ***
*** Bug 102055 has been marked as a duplicate of this bug. ***
*** Bug 115042 has been marked as a duplicate of this bug. ***
Don't see a question for design/UX here (added the flag myself). Would be nice to have, given that the format doesn't limit us. So up to dev.
Any hope for this long-standing feature request to receive any attention? There have been several duplicate reports and the ability to insert "Custom Properties" fields in Draw/Impress is a basic feature in a professional setting for e.g. making drawing headers, document/revision identifiers etc. It already works well in Writer, but is inconsistently missing in Draw/Impress. We are currently attempting to use LO instead of MSO at our company, but having to manually update fields at each page is a hassle yielding negative perception towards LO. Is there a place, where you can offer monetary support towards getting this specific feature implemented?
LibreOffice is a volunteer-driven open source project. We do not have a development plan in the usual sense. To draw more attention on a particular ticket you can a) precisely describe the use case and make sure it's not a demand from a small portion of users, b) consolidate the requests as done with duplicates (QA will raise the importance after some threshold), and c) suggest a solution. You can get professional support from our ecosystem partners, see https://www.libreoffice.org/download/libreoffice-in-business/
*** Bug 149929 has been marked as a duplicate of this bug. ***
*** Bug 151099 has been marked as a duplicate of this bug. ***
*** Bug 147850 has been marked as a duplicate of this bug. ***
*** Bug 102373 has been marked as a duplicate of this bug. ***
*** Bug 161002 has been marked as a duplicate of this bug. ***
*** Bug 151895 has been marked as a duplicate of this bug. ***
*** Bug 169161 has been marked as a duplicate of this bug. ***
*** Bug 170414 has been marked as a duplicate of this bug. ***
I have a concrete modern use case for this feature. LibreOffice Writer supports database fields and mail merge, but it is not suitable for visually rich or typographic layouts such as cards, flashcards, badges, certificates, posters or educational material. Writer is based on a flowing text model and page-oriented structure, which makes it difficult to: - precisely position objects - design visually consistent layouts - control alignment and spacing reliably - work with complex graphics and backgrounds LibreOffice Draw is the natural tool for these layouts because it provides: - absolute positioning of objects - vector graphics and shapes - layers and alignment tools - better control over images and backgrounds However, Draw currently lacks database fields and any form of data-driven duplication of pages or objects. This creates a functional gap in LibreOffice: Writer can do data merge but not graphic layout, while Draw can do graphic layout but not data merge. Adding database fields and serial duplication to Draw would enable professional-grade batch production of cards, flashcards, badges, certificates, posters and game components from spreadsheet data. This is a real-world workflow limitation today, not a theoretical request.
This feature is requested by many users, not just a few. You can see this because similar requests come up again and again over the years. Please notice that this is a real need, not just a one-time idea. Why not acknowledge that users really want this? At least give an official answer if it is possible or not, and why. Thank you.