Problem description: Steps to reproduce: 1. Connect to a postgresql database 2. Define a simple report with a group section 3. Try do define a counter or a accumulation inside the group before and after section In some cases, also the group detail is not working anymore. Opening a report created by previous release it works, including details, count and accumulators. Current behavior: Expected behavior: Operating System: Fedora Version: 4.1.1.2 rc
Is this only a problem with Postgresql? If not it could be tested by everybody. Is it the grouping, that didn't work in your system any more, or are the functions "counter" and "accumulation" destroyed?
No. I think the problem is on the managing of the dialog boxes involved into the definition of the grouping field. That's why a odb created with a previous version (4.1.0) just work (if you have not to modify it). 2013/8/27 <bugzilla-daemon@freedesktop.org> > robert@familiegrosskopf.de changed bug 68619<https://bugs.freedesktop.org/show_bug.cgi?id=68619> > What Removed Added CC robert@familiegrosskopf.de > > *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=68619#c1> on bug > 68619 <https://bugs.freedesktop.org/show_bug.cgi?id=68619> from > robert@familiegrosskopf.de * > > Is this only a problem with Postgresql? If not it could be tested by everybody. > > Is it the grouping, that didn't work in your system any more, or are the > functions "counter" and "accumulation" destroyed? > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
I have tested it with the internal HSQLDB. Created a report, grouped it, set a counter in the Detail-section. Multiplicated two fields in the detail-section. In the group-footer: Get the sum of the multiplicated fields by a user-defined function. Get the accumulation of one field. Everything works well with LO 4.1.1.2 an OpenSUSE 12.3 64bit rpm. You have written: > "That's why a odb created with a > previous version (4.1.0) just work (if you have not to modify it)." Could it be you created something with label-fields, which doesn't match the functionality. This had been broken since 4.1.0.0 beta2 and works right with 4.1.1.2 https://bugs.freedesktop.org/show_bug.cgi?id=67109
I have never tried with the internal hsqldb, but only with postgresql. I will try to rebuild the bug with a very simple table and I will post the results. Thanks. 2013/8/28 <bugzilla-daemon@freedesktop.org> > *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=68619#c3> on bug > 68619 <https://bugs.freedesktop.org/show_bug.cgi?id=68619> from > robert@familiegrosskopf.de * > > I have tested it with the internal HSQLDB. Created a report, grouped it, set a > counter in the Detail-section. Multiplicated two fields in the detail-section. > In the group-footer: > Get the sum of the multiplicated fields by a user-defined function. Get the > accumulation of one field. > Everything works well with LO 4.1.1.2 an OpenSUSE 12.3 64bit rpm. > > You have written: > > "That's why a odb created with a > > previous version (4.1.0) just work (if you have not to modify it)." > > Could it be you created something with label-fields, which doesn't match the > functionality. This had been broken since 4.1.0.0 beta2 and works right with > 4.1.1.2https://bugs.freedesktop.org/show_bug.cgi?id=67109 > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
It seems that building a report from scratch the system is working, but I can confirm the problem on my database, coming from an older version of openoffice. I'm trying to duplicate the problem changing the datasource. In this way I can put the odb file as an attachment of the bug. Stand by until I will be able to upload the file. Bye. 2013/8/28 <bugzilla-daemon@freedesktop.org> > *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=68619#c3> on bug > 68619 <https://bugs.freedesktop.org/show_bug.cgi?id=68619> from > robert@familiegrosskopf.de * > > I have tested it with the internal HSQLDB. Created a report, grouped it, set a > counter in the Detail-section. Multiplicated two fields in the detail-section. > In the group-footer: > Get the sum of the multiplicated fields by a user-defined function. Get the > accumulation of one field. > Everything works well with LO 4.1.1.2 an OpenSUSE 12.3 64bit rpm. > > You have written: > > "That's why a odb created with a > > previous version (4.1.0) just work (if you have not to modify it)." > > Could it be you created something with label-fields, which doesn't match the > functionality. This had been broken since 4.1.0.0 beta2 and works right with > 4.1.1.2https://bugs.freedesktop.org/show_bug.cgi?id=67109 > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
Created attachment 84896 [details] The data source
Created attachment 84897 [details] The odb file
I have reproduced the problem, working on my original odb file. Now it get data from a Spreadsheet. - open the db Ammin.odb - change the source to AmminSrc.ods correct path - try to modify Rapporto1 adding a function sum in the footer of the group wap_azienda1 (which is already defined with a working counter), using the add text field option - On this field, try do sum esp-anno or something else numeric - After the choice SUM the dialog boxes are reset and swith to user functions BY the way, this is what my openoffice does. I have tried to change from italian to english the interface, but i have the same behaviour.
(In reply to comment #8) > - On this field, try do sum esp-anno or something else numeric > - After the choice SUM the dialog boxes are reset and swith to user functions > What should be wrong with this behavior? LO creates a user-function, which builds a sum. I could see the same behavior in LO 3.3.4 and in LO 4.1.1.2.
Created attachment 84997 [details] attachment-21116-0.html In a new database, selecting the sum field I see in the data property Function, Table field, Sum, and context group. In the example I uploaded, I just see a User Function and it's name. In effect it works, but when opening a report for maintenance, the end user does not understand clearly what is running on the field. Finally, if you play with the dialog, you see that the functions are nested and the end-user is not able to manage the definition. In the first example, a report showing the data section correctly. In the second, a nested data section. In my opinion the exact behaviour odb has to use is the first. Franco. 2013/8/30 <bugzilla-daemon@freedesktop.org> > *Comment # 9 <https://bugs.freedesktop.org/show_bug.cgi?id=68619#c9> on bug > 68619 <https://bugs.freedesktop.org/show_bug.cgi?id=68619> from > robert@familiegrosskopf.de * > > (In reply to comment #8 <https://bugs.freedesktop.org/show_bug.cgi?id=68619#c8>) > > - On this field, try do sum esp-anno or something else numeric > > - After the choice SUM the dialog boxes are reset and swith to user functions > > > What should be wrong with this behavior? LO creates a user-function, which > builds a sum. I could see the same behavior in LO 3.3.4 and in LO 4.1.1.2. > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
Created attachment 84998 [details] attachment-21116-1.dat
Created attachment 84999 [details] Schermata da 2013-09-01 11:19:25.png
Created attachment 85000 [details] Schermata da 2013-09-01 11:20:30.png
I must test a little bit. I can reproduce this behavior with the attached example, but I can't reproduce it with a *.odb-file I created by myself. There it looks always like https://bugs.freedesktop.org/attachment.cgi?id=84999.
@Franco : have you tested with a recent 4322 production release to whether the problem is still present for you ?
Have tested it now with LO 4.3.3.1, OpenSUSE 64bit rpm Linux. If you use a function like "Sum" and in the datafield the created function is shown - not the data, which is used. Also isn't shown the function and the group, where the function is made for. The function itself doesn't work. You couldn't find the created function in the report-navigator. Seems there is something else broken. Will have a look where this appears the first time.
I have now tried it with many versions here. The functions defined as Data-field-type function doesn't work in any version of LO with an old database. There isn't created a function. There isn't shown the field for the function and the group, where it is defined for. Tested with every main-version down to LO 3.3.4 - doesn't work. Will try a little bit more later.
Now I tried with a new created database. Took different fields with Integer, SmallInteger and someone else. Put some content in the table and started the Report-Builder. With this database all will work with the same LO- and system-environment.Will try to remove all content of the not-working-database and then try it again.
Have now tried it with different files. Sometimes I could reproduce there isn't created any function. In one file I first couldn't create any function, then I deleted all Macros (deleted the Basic-Folder in the *.odb-file), renamed the database and then I could create the functions. But I could only define a accumulation shown in the right way as created by the report-builder, not user-defined with an accumulation of a Integer-value. In the same report a decimal-value will be accumulated, but a user-defined function will be created. Seems to be a little bit tricky to find the relation between the different parts of the database and the handling of functions in the report-builder.
Created attachment 108302 [details] Functions in the report - Accumulation with some fields only user-defined Open the report for editing. Have a look at the different functions in the group-footer. All functions had been created by the Report-Builder. The functions of the fields on the right side look like user-defined functions. Only the fieldname differs from the other functions. If the fieldname has characters like "_" or "-" the function is created as user-defined function. Could be it is the same with many other special characters. I haven't tested more than this.
Changed the version to "Inherited From OOo", because the bug could be reproduced with LO 3.3.0beta1 also.
Adding self to CC if not already on
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Bug still exists in LO 5.1.0.2, OpenSUSE Leap 42.1 64bit rpm Linux. Bug only appears while filednames have special characters like "_" or "-". Have changed the title a little bit for this.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Bug still exists in LO 5.3.1.1, OpenSUSE Leap 42.1 64bit rpm Linux.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists with LO 6.0.5.2, OpenSUSE 42.3 Leap, 64bit rpm Linux.
Dear franco.violi, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists with LO 6.2.4.2 on OpenSUSE 15 64bit rpm Linux
Dear franco.violi, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists with LO 7.1.4.2, OpenSUSE 15.2 64bit rpm Linux
Dear franco.violi, 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