Bug 107896 - MAILMERGE : "Exchange database" misses "next record" fields
Summary: MAILMERGE : "Exchange database" misses "next record" fields
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Mail-Merge
  Show dependency treegraph
Reported: 2017-05-16 16:26 UTC by marc
Modified: 2023-02-01 03:20 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Mailmerge Document base (21.58 KB, application/vnd.oasis.opendocument.text)
2017-05-22 19:03 UTC, marc
Base database (31.36 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-05-22 19:04 UTC, marc
Second database (31.36 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-05-22 19:05 UTC, marc
Mailmerge Document after changing database (21.94 KB, application/vnd.oasis.opendocument.text)
2017-05-22 19:06 UTC, marc

Note You need to log in before you can comment on or make changes to this bug.
Description marc 2017-05-16 16:26:11 UTC
Document is a set of stickers thus using "next record" field in all but the first box.
If I change source database using the "exchange database" from "Edit" Menu to a new one with a different registered name, e.g. "Catalogue1" to "Catalogue2", the "exchange database" recalculates all fields names to bind to Catalogue2. 
Catalogue1.table.field become Catalogue2.table.field
However, "Next Record:Catalogue1.table" remains "Next Record:Catalogue1.table".

Steps to Reproduce:
1. see description

Actual Results:  
Data fields are properly processed but not the "next record" field.
"Next Record:Catalogue1.table" remains "Next Record:Catalogue1.table".

Expected Results:
"Next Record:Catalogue1.table" should become "Next Record:Catalogue2.table".

Reproducible: Always

User Profile Reset: No but have it on several computers.

Additional Info:

User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
Comment 1 Buovjaga 2017-05-22 16:35:02 UTC
Could you provide minimal document and database files so testers can test more efficiently?

Change back to UNCONFIRMED after you have provided the files.
Comment 2 marc 2017-05-22 19:03:31 UTC
Created attachment 133458 [details]
Mailmerge Document base
Comment 3 marc 2017-05-22 19:04:20 UTC
Created attachment 133459 [details]
Base database
Comment 4 marc 2017-05-22 19:05:12 UTC
Created attachment 133460 [details]
Second database

actually it's just a copy of the base database Catalogue.ods
Comment 5 marc 2017-05-22 19:06:28 UTC
Created attachment 133461 [details]
Mailmerge Document after changing database

"Catalogue" became "Catalogue2" for data fields but remained "Catalogue" for "Next records" fields.
Comment 6 Roman Kuznetsov 2018-06-14 19:21:31 UTC
Mike, please look at this bug
Comment 7 Dieter 2019-01-17 21:56:18 UTC
Marc, some new releases of LibreOffice are available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?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.
Comment 8 marc 2019-03-09 18:39:59 UTC
I confirm the bug is still there in both : my regular install : snap install

sorry for the late reply.
Comment 9 Buovjaga 2019-03-24 17:00:03 UTC
marc: can you explain in more detail, how we should test with your attached files?

Here are my steps so far:
1. Open Stickers.odt
2. Edit - Exchange database - Browse - Catalogue.ods
3. Edit - Exchange database - Browse - Catalogue2.ods

Now what should I look at? I see the Next record fields are the empty grey blocks at the top of Auteur fields, but how can I confirm this: "Next Record:Catalogue1.table" remains "Next Record:Catalogue1.table"
Comment 10 marc 2019-03-24 21:33:48 UTC
Sorry, I forgot to mention that you should enable Menu / View / "Field Names" to actually see that the database reference part changes for all fields but the "Next Record".

So full scenario should be
1. Open Stickers.odt
2. enable View / "Field Names"
3. Edit - Exchange database - Browse - Catalogue.ods
4. Edit - Exchange database - Browse - Catalogue2.ods
Comment 11 Buovjaga 2019-03-25 08:04:14 UTC
Thanks, now I was able to confirm.

Arch Linux 64-bit
Build ID: 66b21521a95f7b2053aa99a23e0a4c34438af6c7
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 22 March 2019
Comment 12 QA Administrators 2023-02-01 03:20:33 UTC
Dear marc,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team