Bug 131371 - FILEOPEN DOCX Mail merge data source information not used (<w:connectString)
Summary: FILEOPEN DOCX Mail merge data source information not used (<w:connectString)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: Mail-Merge 132835
  Show dependency treegraph
 
Reported: 2020-03-16 07:51 UTC by NISZ LibreOffice Team
Modified: 2023-05-07 03:16 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Example base document file from Word (17.98 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-03-16 07:52 UTC, NISZ LibreOffice Team
Details
Example data source from Excel (8.11 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2020-03-16 07:53 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word – tries to query the data source (8.61 KB, image/png)
2020-03-16 07:53 UTC, NISZ LibreOffice Team
Details
Screenshot of the problem in Writer – does not query the data source (49.94 KB, image/png)
2020-03-16 07:53 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2020-03-16 07:51:08 UTC
Description:
When creating a mail merge base document and defining data source fields in Word, it also saves information about the file in word/settings.xml.
This can be used to set up data source for example on a different computer with access to the same base document and data source, Word does this.
Writer cannot, and we also lose the information on saving the file as docx (that is worth another bug).

Steps to Reproduce:
1. Open attached docx file in Word and Writer

Actual Results:
Word tries to set up the data source connection, and if successful, it shows the merged data in the form letter.

Expected Results:
Writer should try to set up the data source based on the available information.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: cf96cb11e2a46c452a273ded1c66c556118983cf
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: CL
Comment 1 NISZ LibreOffice Team 2020-03-16 07:52:47 UTC
Created attachment 158711 [details]
Example base document file from Word
Comment 2 NISZ LibreOffice Team 2020-03-16 07:53:04 UTC
Created attachment 158712 [details]
Example data source from Excel
Comment 3 NISZ LibreOffice Team 2020-03-16 07:53:24 UTC
Created attachment 158713 [details]
Screenshot of the original document side by side in Word – tries to query the data source
Comment 4 NISZ LibreOffice Team 2020-03-16 07:53:45 UTC
Created attachment 158714 [details]
Screenshot of the problem in Writer – does not query the data source
Comment 5 Xisco Faulí 2020-03-19 11:51:28 UTC
Moving to NEW
Comment 6 NISZ LibreOffice Team 2021-05-06 13:26:51 UTC
An earlier attempt to import such settings is in gerrit: https://gerrit.libreoffice.org/c/core/+/45537
Comment 7 QA Administrators 2023-05-07 03:16:37 UTC
Dear NISZ LibreOffice Team,

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