https://bugs.documentfoundation.org/show_bug.cgi?id=149497

            Bug ID: 149497
           Summary: CALC Enhancement. Permit "No User Input" as a data
                    validation which would then permit filter sorting
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Description:
If a cell in a filtered array is defined as protected then sorting of the array
is prohibited.
The reason for this is stated as "It is not possible to sort / reorder
protected rows, because by doing that the cells would change their contents
(example: the value at cell A1 - that is, column A, row 1 - would be moved to
another row). (Also, the sorting options in the autofilter menu do the same
that the sorting tools in the toolbars.)"
If the entire row is based upon recalculating values contained entirely within
that row or with absolute addresses from outside the filtered array then the
above excuse seems flawed.
If an additional data validation of "No User Input" were assigned to a cell or
group of cells then acceptable checks and balances could be included in the
formulae for those cells.
Seems like a simple Win-Win scenario to me.


Steps to Reproduce:
Enhancement Suggestion

Actual Results:
Current dogma prevents many valid simple sorting requests on validated cells

Expected Results:
Ability to prevent user errors in formulaic cells whilst still permitting
autofilter operations on a defined array.


Reproducible: Always


User Profile Reset: No



Additional Info:
But probably not relevant

Version: 7.2.7.2 (x64) / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: sv-SE (en_GB); UI: en-GB
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to