Bug 124716 - Pivot table's page field's cell data type does not match type of value in data source
Summary: Pivot table's page field's cell data type does not match type of value in dat...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:xlsx
Depends on:
Blocks: Pivot-Table-XLSX
  Show dependency treegraph
Reported: 2019-04-13 09:58 UTC by Mike Kaganski
Modified: 2021-10-13 03:40 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

A simple pivot table with filter on mixed-type content (14.84 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2019-04-13 09:58 UTC, Mike Kaganski

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2019-04-13 09:58:00 UTC
Created attachment 150727 [details]
A simple pivot table with filter on mixed-type content

In the attached spreadsheet, week # is used to filter data in the pivot table (page field). Excel sets cell B1 data type based on which data type was in the data source; so when selecting week 1, =FORMULATEXT(B1) returns TRUE, and for week 2 (which is made text in the data source) it returns FALSE. Using B1 in LOOKUP also succeeds for week 1 when searching over numbers; but fails (correctly) for week 2.
In LibreOffice, the type of B1 is unconditionally text. LOOKUP fails for any week used in the filter.

See https://ask.libreoffice.org/en/question/190242 for real-life problem because of this.
Comment 1 m.a.riosv 2019-04-13 23:02:28 UTC
It happens also with dates, may be some relation, as example dates in GETPIVOTDATE() must be introduced as text in the criteria. 
Version: (x64)
Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: es-ES (es_ES); UI-Language: en-US
Calc: CL
Comment 2 QA Administrators 2021-10-13 03:40:37 UTC
Dear Mike Kaganski,

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team