After creating a Base query to filer MSSQL using JDBC, BASE shows all the correct data. When it is used in a mail merge, text fields show no data. Numeric and logical fields are displayed.
Steps to Reproduce:
1. Connect a mssql database to Base using JDBC
2. Create a base query to create some results
3. Go to writer and execute a mail merge against the query
Missing data on text fields
Data is populated and merged from text fields
User Profile Reset: No
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Has this worked in an earlier version?
Does the problem still appear in 5.3?
Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
I am not aware that this has worked in an earlier version. I have not attempted 5.3, but I will test it.
Created attachment 131732 [details]
Base Query Example
This is a base query with some fields that is extracted from JDBC MSSQL.
Created attachment 131733 [details]
Document containing merge fields
This shows employee #, first and last name. Note that if I go to Writer and View/Data Sources, it sees the contents of the base query correctly.
Created attachment 131734 [details]
Notice that the integer field of the employee # shows in the merge, but where is first name and last name? Text fields do not appear in the merge. If I make a spreadsheet from this query and merge from the spreadsheet, it works. Writer doesn't work directly correctly from the Base query.
It seems, that nobody could confirm this bug for more than 18 month. And also no comments were made during this timeframe. So I‘d like to ask, if it is still reproducible for you.
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.
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker