Bug 247727 - kspreadsheet:msoffice2007: Cell with "NULL" error is shown as 0
Summary: kspreadsheet:msoffice2007: Cell with "NULL" error is shown as 0
Status: RESOLVED WORKSFORME
Alias: None
Product: calligracommon
Classification: Applications
Component: filters (other bugs)
Version First Reported In: Git
Platform: All
: NOR normal
Target Milestone: ---
Assignee: Calligra Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-10 07:08 UTC by Lassi Nieminen
Modified: 2023-01-20 05:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Test data to be opened in kspread (7.69 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2010-02-10 07:08 UTC, Lassi Nieminen
Details
Screen shot when viewed in kspread (180.83 KB, image/pjpeg)
2010-02-10 07:09 UTC, Lassi Nieminen
Details
Screen shot when viewed in msoffice 2007 (109.88 KB, image/pjpeg)
2010-02-10 07:09 UTC, Lassi Nieminen
Details
pyodconverter converted testdata (8.56 KB, application/x-zip-compressed)
2010-03-04 12:13 UTC, Lassi Nieminen
Details
koconverter converted testdata (169 bytes, application/x-zip-compressed)
2010-03-04 12:13 UTC, Lassi Nieminen
Details
koconverter converted testdata opened in openoffice (87.51 KB, image/x-png)
2010-03-04 12:14 UTC, Lassi Nieminen
Details
pyodconverter converted testdata opened in koffice (83.56 KB, image/x-png)
2010-03-04 12:17 UTC, Lassi Nieminen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Faure 2010-08-13 20:37:51 UTC


---- Reported by lassi.ta.nieminen@nokia.com 2010-02-10 08:08:49 +0200 ----

Created an attachment
Test data to be opened in kspread

Test data cretaed in MSexcel 2007

SOFTWARE VERSION:
  Kubuntu 9.04
  Koffice (svn version 1086882)
  Test document (MS excel 2007): me07_null_error

HARDWARE VERSION:

PRECONDITIONS: 

STEPS LEADING TO PROBLEM: 
  1. Open the attached document in MS excel 2007.
  2. Open the same document in KSpread.
  3. Observe that Cell with "#NULL" error is displayed as 0

EXPECTED OUTCOME:
Error value in cell should be displayed as "#NULL"
ACTUAL OUTCOME:
"#NULL" error is displayed as 0
FREQUENCY OF OCCURRENCE: 
always



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-02-10 08:09:32 +0200 ----

Created an attachment
Screen shot when viewed in kspread



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-02-10 08:09:54 +0200 ----

Created an attachment
Screen shot when viewed in msoffice 2007



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-04 13:13:28 +0200 ----

Created an attachment
pyodconverter converted testdata



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-04 13:13:50 +0200 ----

Created an attachment
koconverter converted testdata



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-04 13:14:13 +0200 ----

Created an attachment
koconverter converted testdata opened in openoffice



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-04 13:17:16 +0200 ----

Created an attachment
pyodconverter converted testdata opened in koffice

Observation (1096327) : File got corrupted when converted using koconverter and when loaded in open office error message is displayed.

KOffice loaded the OOo-converted document correctly.



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-19 18:48:02 +0200 ----

Working on this.



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-25 15:45:42 +0200 ----

At this report we see the same bug as in the https://projects.noname.org/bugzilla/show_bug.cgi?id=135295 that is, that a recalculation does change the displayed value what happens cause KSpread does not initial recalculate after loading a document but trusts in the cached value provided with the document. This is a problem cause a simple recalc of the document can change calculation results what should never happen.



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-03-29 19:22:01 +0300 ----

Cell now shows "#PARSE" instead of "0" when the formula is not valid. Fixed in
r1108708.



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-04-06 13:01:58 +0300 ----

Discussed with developer. #NULL should be displayed instead of #PARSE.
Tested in rev 1111565
Reopening.



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-04-06 13:03:18 +0300 ----

The problem here is that the cell D6 contains "=OR(A55  A56)" where the spaces between A55 and A56 mean intersection (grep for intersect in the kspread sources). If we remove one space and change the formula to "=OR(A55 A56)" then the correct value (that is #NULL!) is displayed. That means that the bug is within the formula.cpp parser which needs to compress multiple intersect operators into one.



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-04-22 00:47:54 +0300 ----

The correct fix would be to fix the xlsx filter to convert the intersection operator to ! as is defined in odf/openformula (and that fix would be far from trivial I guess), not to make kspread understand ' ' as intersection operator. Odf and OOo both define ! as the intersection operator.



--- Bug imported by faure@kde.org 2010-08-13 20:37  ---

This bug was previously known as _bug_ 156320.

Imported an attachment (id=50352)
Imported an attachment (id=50353)
Imported an attachment (id=50354)
Imported an attachment (id=50355)
Imported an attachment (id=50356)
Imported an attachment (id=50357)
Imported an attachment (id=50358)

Unknown milestone "2010-11 in product koffice. 
   Setting to default milestone for this product, "---".
Bug Status was REOPENED but everconfirmed was false
   Setting status to UNCONFIRMED

Comment 1 Andrew Crouthamel 2018-11-09 00:56:56 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-18 03:32:18 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-21 23:58:19 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-05 05:25:06 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-01-20 05:08:28 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!