Bug 46041 - printing address labels in writer using external database 'next dataset' is ignored
Summary: printing address labels in writer using external database 'next dataset' is i...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-14 06:27 UTC by Gerd
Modified: 2013-07-08 21:22 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerd 2012-02-14 06:27:45 UTC
While printing address labels with a table in writer using external database 'next dataset' is ignored. (to be exact: using the German language version. 'naechster datansatz' is ignored.) The result is many sheets of address labels where on every sheet all labels are filled with one dataset. Next sheet is filled with next dataset data.
This bug had occurred already with 3.4.3 but not with 3.4.5 version
Comment 1 sasha.libreoffice 2012-02-22 05:45:25 UTC
Thanks for bugreport
Please, verify if this bug exist in 3.5.0 version of LibreOffice
Comment 2 Joel Madero 2012-10-23 17:26:51 UTC
Please provide a sample packet for us to test on so we can confirm exact behavior. 

It would be nice to have 

a) a test document that we can merge to a source

b) the source, a database that we can attach to

This will make it so that we confirm exactly what you see. Also please provide exact steps you use when attaching to the database, etc...

The more information the better (well, within reason ;) ). Thanks for helping us out. Marking as NEEDINFO, once you provide the attachment(s) please mark as UNCONFIRMED and I'll reproduce the bug and triage it
Comment 3 Joel Madero 2013-05-30 16:17:29 UTC
Dear Bug Submitter,

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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
Comment 4 QA Administrators 2013-07-08 21:22:33 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO