Problem description: due to Help "Only records selected by a multiple selection in the data source view are considered". In fact, all records from dataset are considered. And with strange indexing: record number of first record in dataset is 2, second is 3, and so on... Steps to reproduce: 1. Insert into text doc database field: Insert - Fields - Other..., Database tab, Type set to "Any record", Record number set to 2 2. Insert into text field(s) of type "Mail merge field" from some dataset 3. Open data sources: View - Data Sources 4. In data source select two or greater records, start from second or greater 5. Click button "Data to Fields" Current behavior: The values of first record of dataset are inserted into fields Expected behavior:The values of second record of a multiple selection must be inserted into fields Operating System: Ubuntu Version: 4.1.3.2 release
Windows 7 LibreOffice 4.1.0.4 the same bug.
Windows 7 Apache OpenOffice 4.0.1 have the same bug.
Can you please provide a test document so this can be tested against and subsequently be confirmed. If your document contains sensitive data, please clear that or replace it with random information. A step-by-step description of how to reproduce the issue is most helpful and will help to speed up the processing of this problem a lot. Setting to NEEDINFO until more detail is provided. After providing the requested info, please reset this bug to UNCONFIRMED. Thanks :) Also OS > ALL since this seems to be happening on Windows too.
Created attachment 91292 [details] Database file to use in mergemail
Created attachment 91293 [details] Text doc i used to test mailmerge fail.
Comment on attachment 91293 [details] Text doc i used to test mailmerge fail. By using the wizard, the "Insert Address Block" step, there is an error in selecting a database created with the help of the wizard. It is observed that the field called "table" wizard does not store the value, and therefore the accept button is not activated. Al usar el wizard, en el paso "Insertar Bloque de direcciones", existe un error al seleccionar una base de datos creada con la ayuda de el wizard. Se observa que el campo llamado "tabla" del wizard no almacena valor, y por tanto el botón de aceptar no se activa.
Confirmed on LO 4322 OSX Yosemite
How to reproduce : 1) Download ODT and ODB files. Open both in LO. 2) In Writer document, remove all previously inserted fields. 3) Insert > Field > Other > Database 4) Insert Field1 into Writer document, press space key 5) Insdert Field2 into Writer document, press return key 6) Press F4 key, select any tuple greater than the first one, e.g. the second tuple 7) Click on the "Data to Fields" icon 8) See how only data from first record gets inserted What should happen : selected tuple data should be inserted.
Reproduced also in Version: 4.4.0.0.alpha0+ Build ID: d807cba9ee60cb1404b54addf9cd3e54de89f331
Jan-Marek/Lubos: seeing branches like "private/jmux/mailmerge-fixes", "private/llunak/mailmerge_01", I thought you might be interested in this one.
Note that if you drag and drop the field headers from the data source browser instead of using Insert > Field, the selected tuple is inserted correctly
I see the problem in 3672 as well
When I follow Alex's instructions, the fields just end up empty (or just a space?), whether I take the first or any other record, and whether I use the drag-and-drop method or insert / field. master (4.4.0.alpha) build of 26 sep 2014.
(In reply to Alex Thurgood from comment #11) > Note that if you drag and drop the field headers from the data source > browser instead of using Insert > Field, the selected tuple is inserted > correctly It is inserted as text, not as field
Screen capturing available by following link: http://youtu.be/-MAFQkGS3eI
Adding self to CC if not already on
Oliver Specht committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=f5ccfd60c2c5dab392d58870fbd079a6286bc239 tdf#73025: set absolute database index fixed It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Hi, Is this bug fixed? If so, could you please close it? Regards
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear mishich, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I tried to test, but I couldn't confirm the report. It's either fixed or needs a new status. Since nobody responded to QA ping, I'll close. But it would be useful to retest this.