When we print a Writer document with database fields, it asks: "Your document contains address database fields. Do you want to print a form letter?"
But, we cannot chooses which pages to print and it prints all.
We should have a dialog to choose which pages from document to print.
@Timur - can you provide clear steps on how to get to that dialog. Also a sample document would help.
Setting to NEEDINFO - once you provide info please set to UNCONFIRMED. Thanks
Created attachment 110046 [details]
Simple ODT mailmerge example with 1 field and 2 pages
1. Open new Writer document and add 2nd page
2. Turn on View-Data Sources
3. From built-in Bibliography data source with 20 records, add Author field to the document on the 1st page
4. Choose File-Print to print document with database fields (20 copies) and Yes to print a form letter
5. You can choose Records and Output but not pages from the document to print so it will print all pages x number of records
Created attachment 110960 [details]
Pages and Ranges: example added to mailmerge Print dialog
I put here "Inherited from OO". There've been some improvements through development, because OO prints forms badly, but neither can choose pages.
I add an example image how mailmerge print dialog might look like with standard Pages and Ranges print section.
One for the UX folks :-)
Adding self to CC if not already on
Created attachment 115796 [details]
mailmerge Print dialog example: added Pages and Ranges and Output
We're replacing our use of the 'ux-advise' component with a keyword:
Component -> LibreOffice
Add Keyword: needsUXEval
What meaning does it have when you print based on a database with a selection of entries and then limit the output to a specific page? I mean you print from 1 to 2 in the attached file, which creates four pages, and why would you want to actually print only the first 3 pages? Is there a use case?
If there is a good reason you may go with the suggestion (removing UX). Otherwise my personal choice would be to not implement this option. You may face issues for the implementation when, for instance, from/to is set to some value and the page count has to get updated reliably.
Btw1: <strikethrough>I don't see how "Selected records" can be enabled.</strikethrough> The first column should indicate that it may get selected; or multiselection is possible per ctrl/shift (selecting the whole column).
Btw2: Like "Print to PDF" (bug 86668) the Preview does not deal with the fact of fields in the document. On the other hand, if there is no good use case for Print to PDF or Preview without merging the db fields we could disable the functions and make them available in the mail merge dialog as Preview next to Ok, and PDF as part of output = file (exists).
Btw3, "Explorer off" by default makes the dialog easier to understand (you should know what table is being used in this document). And stripping edit functions would also streamline the user experience. Not sure if editing is needed shortly before the document is going to the printer. Rather you put more effort in the filter because after closing the overlay dialog you have no clue about the actual filter parameter.
Btw4: Sorry for the delay. Shouldn't take two years to get an answer.
Personally I use the same documents for mailmerge repeatedly, I just copy the previous to the top, change and print (instead of making a separate new document each time).
Also, in some other case, I keep notes and preparation stuff in the same document as final mailmerge, so I don't print all. Workaround is to temporary delete that before printing but it's not safe, one may save it.
The reason why I created attachment 115796 [details] instead of attachment 110960 [details] is in Bug 91377.
Apparently I was wrong and the proposal makes sense. Did a quick poll with the community https://plus.google.com/107566594492891737454/posts/jW1cXUDEgtt, and while many do not known the feature mail merge more than 50% of the yes/no replies agree with the idea to have more print options.
Please add keyword 'needsUXEval' and CC 'email@example.com' if input from UX is needed.