Bug 158264 - Cannot delete formulas from Writer table
Summary: Cannot delete formulas from Writer table
Status: RESOLVED DUPLICATE of bug 72100
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.2.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-18 14:40 UTC by freeware
Modified: 2023-11-26 09:09 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
cannot delete formulas from writer table (790.41 KB, video/mp4)
2023-11-18 14:41 UTC, freeware
Details

Note You need to log in before you can comment on or make changes to this bug.
Description freeware 2023-11-18 14:40:31 UTC
Description:
If you select table cells containing formulas and attempt to delete them by hitting DELETE key, Writer removes some of them, but mostly it leaves some zero values (or broken formulas giving zero as a result) leftovers.
You have to repeat "select and delete" multiple times to actually remove all of the formulas, alternatively you have to remove entire row or column, but that's not an optimal solution to say the least.


Steps to Reproduce:
1. Add formulas to multiple cells in a table
2. Select said cells and hit DELETE

Actual Results:
Selected formulas are NOT deleted correctly.
Most often than not only first selected cell gets deleted, the rest of them are left broken.

Expected Results:
Content of every selected cells should be deleted.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
none
Comment 1 freeware 2023-11-18 14:41:17 UTC
Created attachment 190900 [details]
cannot delete formulas from writer table
Comment 2 nutka 2023-11-18 17:22:48 UTC
@freeware@poczta.fm :

Could you please take a look at Bug 72100?
("EDITING: Deleting contents of cells with formulas in TABLE gives 0 in some cells, and doesn't change other cells in multiple selection").


Comment No. 1 therein provides a possible workaround.

It seems your report could be classified as as duplicate of Bug 72100.
Comment 3 raal 2023-11-26 09:09:03 UTC

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