https://bugs.documentfoundation.org/show_bug.cgi?id=171017
Colin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #18 from Colin <[email protected]> --- (In reply to ady from comment #17) > (In reply to Colin from comment #15) > > Hi @ady I still take issue with the "rejection" of the definition of the slicer fail. An array function creating all its elements on the same row is simply a row of data within the realms of a slicer - just like any other data row. They will all sort to the same result row and if they make absolute references to outside data they will still make absolute references to that outside data. Filter is the perfect example - Simply filter the table on any column and the result will be a display of the entire candidate rows to which the array is attached. What I believe is wrong is that a shotgun approach has been applied to anything that acts upon an array function without the street-wise interpretation that "it's all data on the same row and therefore NOT a single element of an array function". Would you strongly disagree? -- You are receiving this mail because: You are the assignee for the bug.
