Description: When in <wizard print in series ...>, I identify the recipient records that I do not want to be processed with the selection box <exclude recipient>, then running the functions <edit single documents> or <save compound documents> or < print compound documents> from batch print toolbar, I don't get documents with correct recipients. Only in some cases of use of the selection box <exclude recipient> do I get the desired documents. Probably the <send e-mail messages> function also has the same problem. I encountered this problem because I wanted to test the <print wizard ...> function, connecting a database for the recipients of the document, created with Base and containing three records. I also noticed that there are differences in results depending on whether you run first <edit compound documents> and then <save compound documents> and vice versa. It seems to me that the <wizard in series printing ...> function goes completely test in every detail and perhaps even revised in some detail. Actual Results: For instance If I have three recipients and I deselect only the first, I get a document with only the second recipient, without the third, when I run the <save compound documents> function. Expected Results: I expect to get the documents with the recipients determined by the deselection of the unwanted ones, if I have three recipients and I deselect the first I want to get the documents with the second and third recipients. Reproducible: Always User Profile Reset: No Additional Info: This problem occurs with both OpenGL enabled and disabled.
Please write exactly how you use MailMerge. If it's via MailMerge toolbar, we recently had a fix in bug 106959 for document starting with table. Please wait for 7.4.2 and test again or install daily master 7.5+ to test (installs im addition to working LO and doesn't take extensions).
Dear claudio, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Created attachment 186106 [details] documento write per la stampa unione
Created attachment 186107 [details] file base per i campi del documento write
Cosa c'è di errato? La funzione stampa unione non emette sempre i documenti richiesti. Descrizione dell'errore Dopo aver collegato il data base al documento write, e aver collegato i vari campi di write con il data base, se scorro i vari record il documento mi fa correttamente vedere i vari documenti sul desktop per cui la procedura è andata a buon fine, l'errore si materializza quando procedo alla creazione del file o dei file. Se richiedo la stampa unione di tutti i nominativi del data base questa viene eseguita correttamente, ma se ne deseleziono alcuni allora i documenti prodotti non solo quelli voluti. Ho verificato che lo stesso errore si manifesta anche se invece di richiedere file si richiede l'invio di mail. Gravita dell'errore? Molto grave Risoluzione? Semplice revisione del codice sorgente sulle procedure che selezionano i record da usare per la produzione dei documenti finali. Ho allegato i file sui quali ho ottenuto l'errore, così potete velocemente verificare voi stessi quanto segnalo.
Claudio, it seems, that nobody could confirm this bug since more than one year. So I‘d like to ask, if it is still reproducible for you. Could you please try to reproduce it LO 24.2 or with a master build from http://dev-builds.libreoffice.org/daily/master/current.html? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.