Bug 157490 - Updating table cell will remove reference "target" (for cross-reference)
Summary: Updating table cell will remove reference "target" (for cross-reference)
Status: RESOLVED DUPLICATE of bug 157287
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-28 12:42 UTC by thdeppner
Modified: 2023-10-13 14:49 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thdeppner 2023-09-28 12:42:37 UTC
Description:
When updating a table cell that contains a formula (-> https://help.libreoffice.org/7.6/en-US/text/swriter/guide/calculate_intable.html) a cross-reference "target" that has been set for this table cell will disappear. This used to be different; up until LO 7.5.* the referenced cell would just get updated as well as any cross-reference referring to it (as you would expect).

Might be related to this bug: https://bugs.documentfoundation.org/show_bug.cgi?id=157489 

Steps to Reproduce:
1. Have a table cell containing a formula which is set as a reference "target"
2. Cause the formula to update (e.g. by changing a cell that is contained in the formula)
3. See the reference "target" disappear; each cross-reference leading to it displaying "reference not found"

Actual Results:
reference target gets deleted

Expected Results:
reference target just gets updated


Reproducible: Always


User Profile Reset: No

Additional Info:
n/a
Comment 1 Buovjaga 2023-10-11 10:35:10 UTC
No example doc, so can't quickly test, but meanwhile bug 157394 was fixed - do you still see this in 24.2.0 or 7.6.3?

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 2 Stéphane Guillou (stragu) 2023-10-13 14:49:38 UTC
Already tracked in bug 157287, marking as duplicate.

*** This bug has been marked as a duplicate of bug 157287 ***