Description: I have a simple database report that has 2 columns to accumulate for Grand Totals. The items appear to be grouped correctly and I can get totals to appear. One column is correct "credits" and the other column seems to pull a number out of thin air "debits". The source for the report is a query that has already subtotaled the data incoming. Of interest, I deleted the formatted field that was giving me problems thinking it might be glitch or something. When I do this the errant total increases by about 2k. If I didn't know better I would swear there is a variable stored with the report that is not resetting. I am puzzled please help. Steps to Reproduce: 1.just run the report I have set up 2. 3. Actual Results: I get an incorrect total from the accumulation function Expected Results: it should have given the correct total. Reproducible: Always User Profile Reset: Yes Additional Info: I tried restarting in safe mode. This action did not help the function to work correctly.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
@bullbroker: without the report (and the underlying ODB including query on which this is built) then it will be nearly impossible for us to reproduce this behaviour as we don't know exactly what you have done, or how you have done it. Please either provide a sample ODB file with instructions for use as Xisco has requested, or else provide detailed steps on how to reproduce the ODB file containing the associated query and report with instructions on how to use.
Dear bullbroker, 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: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear bullbroker, 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 Warm Regards, QA Team MassPing-NeedInfo-FollowUp