Bug 48765 - Remote ref to cells in LibO-Calc spreadsheet denied in tool (function)
Summary: Remote ref to cells in LibO-Calc spreadsheet denied in tool (function)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
3.4.6 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Cell-Reference
  Show dependency treegraph
Reported: 2012-04-16 04:02 UTC by Pertti Rönnberg
Modified: 2024-03-29 03:14 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

LibreOffice-Calc v.3.4.6 spreadsheet (14.41 KB, application/vnd.oasis.opendocument.spreadsheet)
2012-04-16 04:02 UTC, Pertti Rönnberg
Another error in MULTIPLE.OPERATIONS (8.54 KB, application/vnd.oasis.opendocument.spreadsheet)
2012-08-16 21:31 UTC, Sören

Note You need to log in before you can comment on or make changes to this bug.
Description Pertti Rönnberg 2012-04-16 04:02:44 UTC
Created attachment 60055 [details]
LibreOffice-Calc v.3.4.6 spreadsheet

There is a very interesting an useful tool in LibreO-Calc 'Data/Multiple operations', the same toll is also in OpenO-Calc; in MSExcel it is called DataTable.
Some 3-4 years ago I had with that tool created a calculating process in OpenO-Calc and when I recently recreated the calculation in LibO I noticed that a flexible feature had vanished.
In the 'new' Calc the first cells of both "row input" variable G8 (of G8, H8, H9,..etc.) and "column input" variable F9 (of F9, F10, F11, ..etc.) in the tool's calculation area require a manually inserted value -- the next variables (increasing or decreasing by a difference) can be values calculated by a formula from the value in cell previous cell.

In the "old" calculation these first cells (G8 and F9) could refer to remote cells (values or formulas) which increases the flexibility and the usability of the tool remarkably.

In that same spreadsheet, outside the tool's calculation area, all cells accept remote references in a normal way.
See enclosed attachment.

I cannot think that that negative change has been done deliberately. 

My computers are (a) PC(AMD)-Win7Prof/32bit and Laptop(Intel)-Win7Prem/64bit; LibO3.4.6 in the PC and LibO3.4.5 in the laptop.

Can I myself do anything to go around the issue?

Please, answer by mail soonest.
Best regards
Pertti Rönnberg (Finland)
Comment 1 Roman Eisele 2012-05-03 10:00:10 UTC
This is a Calc issue, therefore changed the 'Component' field accordingly.
Comment 2 Sören 2012-08-12 22:52:48 UTC
Reproduced on

Build ID: 7122e39-92ed229-498d286-15e43b4-d70da21
on Windows 7 Home (64 bit)

The problem seems to be, that the MULTIPLE.OPERATIONS formula can't handle using any of the inputs of the original formula as inputs for the multiple operations. It seems as if it replaces the inputs in the formula by their new value in a "search and replace"-fashion, which gives either circular dependencies or wrong results dependent on the situation.

We will try to fix it (will be our first real attempt for a bugfix, please be patient)
Comment 3 Sören 2012-08-16 21:31:46 UTC
Created attachment 65662 [details]

During the investigation of this bug, we found another closely reltated error:

If one lets one of the input fields of one cell in the multiple operation point to one of the other multiple operation cells, we get the error for circular reference (Error 522) although there is no circular reference and the result should be welldefined.
Comment 4 QA Administrators 2015-01-05 17:52:37 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2015-01-29 11:02:58 UTC

Win 7 Pro 64-bit Version:
Build ID: 784d069cc1d9f1d6e6a4e543a278376ab483d1eb
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-25_23:07:36
Comment 6 QA Administrators 2016-02-21 08:38:18 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2017-03-06 16:13:23 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-12-03 14:02:02 UTC Comment hidden (obsolete)
Comment 9 xyhausen 2020-03-28 20:24:14 UTC
Both attachments still show errors.

Version: (x64)
Build-ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3
CPU-Threads: 2; BS: Windows 10.0 Build 18362; UI-Render: Standard; VCL: win; 
Gebietsschema: en-GB (de_DE); UI-Sprache: de-DE
Comment 10 QA Administrators 2022-03-29 03:59:36 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2024-03-29 03:14:53 UTC
Dear Pertti Rönnberg,

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