Bug 152160 - Printed label's field content mismatch for spreadsheet data source if field added afterwards in Writer
Summary: Printed label's field content mismatch for spreadsheet data source if field a...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Labels-BusinessCards
  Show dependency treegraph
Reported: 2022-11-21 15:55 UTC by Petri H
Modified: 2022-12-07 06:05 UTC (History)
1 user (show)

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

Afterwards added label field indexing error (362.98 KB, image/png)
2022-11-21 15:55 UTC, Petri H

Note You need to log in before you can comment on or make changes to this bug.
Description Petri H 2022-11-21 15:55:59 UTC
Created attachment 183702 [details]
Afterwards added label field indexing error

After successfull File->New->Labels wizard walkthrough, any afterwards added data source fields in Writer are not printed correctly. 

In attached screen shot I have presented spreadsheet data source where I have set content on relevant cells using naming 1x2 (row x column) principle. Label fields, which were added during file->new->labels wizard walkthrough, are printed with correct content. The same label shows incorrect content if field was added afterwards in Writer. 

Afterwards added fields seems to be in an offset, like indexing 0 or 1 bug. This bug is very annoying if you didn't (remember) select all fields correctly in the start and want to do some changes in your label.

How to reproduce:
1. Make sure you have a spreadsheet linked to a database created in base.
2. Walk through File->New->Labels wizard pointing to some database fields by selecting those fields
3. In Writer, add some fields pointing to e.g. the same database cells
4. Print to any printer
Comment 1 Stéphane Guillou (stragu) 2022-11-25 09:27:45 UTC
Thank you, Petri.
Could you please provide example files to test the issue?
Could you also please paste here the details from Help > About LibreOffice?

Thank you!
Comment 2 Petri H 2022-12-07 06:05:29 UTC
Thanks for looking into this Stéphane.

You need to walkthrough the specified procedure to reproduce the bug. 

details from my LibreOffice
Version: (x86) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (sv_SE); UI: en-US
Calc: CL