Bug 74129

Summary: incorrect computations in conditional texts
Product: LibreOffice Reporter: Markus <muellerm>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: major CC: barta, cno, dr, pierre-yves.samyn
Priority: medium    
Version: 4.2.0.1 rc   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: 3 files for demonstration of mail merge bug in LO4201
result.odt

Description Markus 2014-01-27 22:21:46 UTC
Created attachment 92887 [details]
3 files for demonstration of mail merge bug in LO4201

Problem description: Conditional text is not properly computed when mail merge writer document.

(refer to attached zip-file for 3 documents:
- the mail merge template letter (Herma_5056_2_mal_6.odt), 
- the dataset and field names (CG_DG.ods; 6 records) and 
- the resulting personalised document (Feldauswertungs_Bug.odt; 2 x 6 address fields with address labels (counted rows first later); only 6 data sets attached leaving the last 6 labels empty)

For the labels generated by record 5 and 6 (the last two labels) it is correct, that the words ' und Herr ' appear in the personalised document (see attached file Feldauswertungs_Bug.odt), because the datafield Name2 (see attached spread sheet (CG_DG.ods)) is not empty. But in every other of the address labels (generated by record 1 to 4) the two words ' und Herr ' should not appear, because here the datafield Name2 is empty.

Likewise the leading blank in record 2 prior to the surname should not appear, because this blank as conditional text should only appear, if the field Vorname1 is NOT empty.

In each version prior to LO 4.2 this was working as intended.
Comment 1 karolus 2014-01-28 08:24:40 UTC
Changed File-typ of Attachment
Comment 2 pierre-yves samyn 2014-06-21 16:44:32 UTC
Hi

I do not reproduce with your documents on windows 7/64 & 
Version: 4.3.0.1
Build ID: 67f5430184326974072b65403ef1d9d934fc4481

See the result.odt attached.

Is it possible for you to test with a newer version ?

I set status to NEEDINFO.

Regards
Pierre-Yves
Comment 3 pierre-yves samyn 2014-06-21 16:45:17 UTC
Created attachment 101490 [details]
result.odt
Comment 4 Markus 2014-06-23 09:40:58 UTC
In 4.3.0.1 and Win 7/64 the problem does not occur anymore.
Comment 5 tommy27 2014-06-23 10:02:44 UTC
nice to hear that Markus, however please do not change version field like you did.

that field should express the first release where the bug appeared, in this case 4.2.0.1, not the last version where the bug is still present nor the version where it has been fixed

moreover when we don't exactly know the exact committ that fixed it, we usually set status to RESOLVED WORKSFORME.

I did the necessary changes here.