Created attachment 147642 [details] Database, document for mailmerging and its result I prepared an embedded Firebird database in LO Base. There I've made a query with "LIST()" function, which concatenates strings at grouping by. I can see results of this query. The problem is in the LO Writer, when I make a Mail Merging from the query results. The whole line with the field made from "LIST()" disappears. I made files to demonstrate this bug.
I found, what was the problem: LIST() returns CLOB data. After I have converted it to VARCHAR, I've got the needed result. So, my suggestion is to make such conversion automatically.
Ah, yes CLOB fields and reportbuilder, already an open issue on that. *** This bug has been marked as a duplicate of bug 115893 ***
After talking with folks on the QA channel and testing HSQL memo fields with the text ODT file linked against an HSQL embedded ODB, verifying the MEMO field there does work properly with Mailmerge setting this as NEW instead of a duplicate. Leaving the Reportbuilder issue under the see also property.
Dear Alex Ander, 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 MassPing-UntouchedBug