Bug 284601 - vlookup does not work
Summary: vlookup does not work
Status: RESOLVED FIXED
Alias: None
Product: calligrasheets
Classification: Applications
Component: filter/xlsx (show other bugs)
Version: 2.4-snapshots
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Calligra Sheets (KSpread) Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-21 09:34 UTC by Silver Salonen
Modified: 2011-12-05 01:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
xlsx worksheet with VLOOKUP formulas (7.60 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2011-10-21 09:34 UTC, Silver Salonen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Silver Salonen 2011-10-21 09:34:10 UTC
Created attachment 64747 [details]
xlsx worksheet with VLOOKUP formulas

Version:           2.4-snapshots (using KDE 4.7.2) 
OS:                Linux

I created a simple .xslx worksheet with some vlookup formulas. LibreOffice parses them just fine, but Calligra Tables gives "#PARSE!" error.

Reproducible: Always

Steps to Reproduce:
Create VLOOKUP formula in Excel, open the file with Calligra and see what happens.

Actual Results:  
Formula does not work.

Expected Results:  
Formula should work.
Comment 1 Alvaro Fernando García 2011-11-11 20:03:49 UTC
Confirmed. Reproducible on:

Version: Calligra Tables 2.4 beta 3, KDE SC 4.7.3 using Qt 4.7.4
OS: Arch Linux (kernel 3.1.0-4)

The first time the file was opened, Tables crashed.
The second time, the cells give "#PARSE!" errors.

The issue happens in a fresh install.
Comment 2 Alvaro Fernando García 2011-11-12 00:57:06 UTC
The mentioned crash was caused by other issue...
Comment 3 Sebastian Sauer 2011-11-16 22:17:14 UTC
There are 2 bugs here;

1. the filter produces the wrong values.

For cell B2 OpenOffice displays
=VLOOKUP(A2,C$1:D$1048576,2,0)
while we display
=VLOOKUP(A2;C:D;2;0)

2. vlookup doesn't work in Tables.

When I change B2 to
=VLOOKUP(A2,C1:D10,2,0)
then it displays "3" while Tables displays a "#PARSE" error.
Comment 4 Sebastian Sauer 2011-11-17 06:48:09 UTC
Fixed with 109ec43af6c5.
Comment 5 Silver Salonen 2011-12-04 10:41:13 UTC
I expected to see the fix in beta4, but I don't. In which release will it be available?
Comment 6 Sebastian Sauer 2011-12-05 01:58:46 UTC
Not sure there. But if it doesn't work on beta4 then the commit was done to late and it will be in beta5.