Summary: | [Mailmerge] Impossible to get a document per record when mail merging in a file | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | sophie <gautier.sophie> |
Component: | Writer | Assignee: | Caolán McNamara <caolanm> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | CC: | angelo.locritani, cno, efroys, gautier.sophie, heinz.repp, LibreOffice, nn.libo, olivier.bietzer, reisi007, ribotb, vitriol_vitriol |
Version: | 3.3.0 release | Keywords: | regression |
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 34184 |
Description
sophie
2011-01-07 07:13:35 UTC
Confirming on Mac OSX. This is a stopper for me. Concrete business example : Patent renewal fee reminders sent to clients. Query database, use query to fill in a template that fits to headed letter paper (so particular formatting), each renewal fee reminder must end up in a separate file, not just for convenience, but because each one is particular to a given client (and stored individually), thereby respecting confidentiality issues. Alex It is also a regression compared to OOo 3.2.1 Changing version to releass because bug still present. *** Bug 34428 has been marked as a duplicate of this bug. *** Can reproduce this in 3.3.1 on Ubuntu *** Bug 35119 has been marked as a duplicate of this bug. *** It's annoying, but I do not believe that it's a critical bug, because function will work fine from Mail Merge Wizard. Only for those who are used to select Addresses manually that alternative will not work. Might be related: Save-Monitor-Message remains empty for me when saving from Print menu, but shows progress when saving from Mail Merge Wizard. @Rainer Bielefeld An option shown in the UI is completely broken, than I think it's a serious bug. I don't us the wizard, like many other (advanced?) users... @Rainer Bielefeld: Unfortunately, function from Mail Merge Wizard DOES NOT WORK fine for me as it seems to be affected by my OOo bug 88451 (mail merge deletes section on save to one, http://openoffice.org/bugzilla/show_bug.cgi?id=88451): it seems to create the individual documents by going through a combined document, all target pages are splitted into two pages. Saving to individual documents did work in OOo 3.2.1 and kept the layout, with LibreOffice 3.3.0/1 I have NO WAY to print my mail merge letters other than using F4, values to fields, print normal, select next row, values to fields, print normal, ... Fortunately I have usually not more than 30 records, so this is possible, it would not work with significantly bigger tables. This IS a show stopper. And about the wizard: I tried to train secretaries to use the wizard, without much success. The straightforward direct approach was much more successful, so I believe most frequent mail merge users will not use the wizard at all, especially in companies. So this regression should be fixed ASAP. @Rainer Bielefeld Is this a critical bug or not depends if LibreOffice should be an amateur software or a professional software? Is this just going to be a software for private use, it's not that important, but if LibreOffice should be a competitor for MS Office and be useful for companies. This is very critical. I am doing mail merge with about 400 records per month and if mail merge is not working, LibreOffice is no option. There is no way I will type in 400 records manually and print them out. And in a business view. Thing should just work. If not, you go for another option, because time is money for businesses. I have been recommended OpenOffice/ LibreOffice for many years, but it has been harder and harder to recommend it since the mail merge wizard has never worked and still not, and now in LibreOffice 3.3.x the workaround is not working either. Which means I using two versions on my computer. I have OOo 3.2.1 and LibreOffice 3.3.1. Print out with the first and work on the last. The workaround in OOo 3.2.1 is as follows: - F4, - drag fields into document, - print normal, - yes to question, - tick of single print outs(very important - we have a professional printer which can fold and staples the print outs, which means, if I don't tick of this, the printer will print all records and then fold them together and staple them together! instead of fold each record and staple them separately), - choose from 1 to n+1(if I only choose to n, it will not print out the n-record), - OK, - check the printer settings(since it doesn't remember the printer settings from time to time). I have been using OOo since version 1 and used different ways of workarounds throughout the versions history. For every new version, I had to find a new way round to mail merge. Bug still present in LO 3.3.2 This bug was already fixed in OOo: http://openoffice.org/bugzilla/show_bug.cgi?id=116336 Bug still present in LibO 3.4rc2 (Windows 7 SP1). (In reply to comment #12) > This bug was already fixed in OOo: > > http://openoffice.org/bugzilla/show_bug.cgi?id=116336 Just in case, developers didn't find it, this is what they changed in OOo to fix this issue: http://hg.services.openoffice.org/DEV300/rev/c82a607f1f92 so hopefully someone will pick this up, as we left 3.3.0 far behind, and still this bug - now correctly classified as critical and as one of the most annoying bugs - failed to attract sufficient attention and is still present in 3.4.1. Wouldn't just porting the OOo changes to LibO do the job already? *** Bug 39335 has been marked as a duplicate of this bug. *** *** Bug 39335 has been marked as a duplicate of this one *** *** Bug 39451 has been marked as a duplicate of this bug. *** http://hg.services.openoffice.org/DEV300/rev/c82a607f1f92 is a combined bunch of changes, the apparent specific bit required is a backport of http://cgit.freedesktop.org/libreoffice/writer/commit/?id=2c284c0d082c4dff8545e51b8b2c58324d59f9b0 backported fix as http://cgit.freedesktop.org/libreoffice/writer/commit/?h=libreoffice-3-4&id=81974ceb030b7209af1a55557e697c8acb339b7c should land in 3.4.3 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.