Bug 60157 - NULL handling when modifying Excel.
Summary: NULL handling when modifying Excel.
Status: RESOLVED REMIND
Alias: None
Product: POI
Classification: Unclassified
Component: XSSF (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-20 14:22 UTC by Sateesh
Modified: 2016-10-20 20:44 UTC (History)
1 user (show)



Attachments
testcase_excel_files (10.91 KB, application/zip)
2016-09-20 14:22 UTC, Sateesh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sateesh 2016-09-20 14:22:31 UTC
Created attachment 34280 [details]
testcase_excel_files

During modifying an existing excel file - If an excel file gets a NULL value as input the original field value of the excel file is retained. If it gets a non-NULL value the old value is replaced with this non-NULL value.

Original excel file: test.xlsx
Output excel file: test.out.xslx

The following values are sent as input to modify "test.xslx"
A2:1000 B2:2000
A3:NULL B3:2001

NULL here means no value.

Now in test.out.xlsx - though cell A3 has input of NULL value, the original value '2' is retained. Instead it should be blank. I see the following output in "test.out.xlsx"

A2:1000 B2:2000
A3:2    B3:2001

instead it should be

A2:1000 B2:2000
A3:NULL B3:2001
Comment 1 Sateesh 2016-09-20 14:24:12 UTC
Version 3.9
Comment 2 Nick Burch 2016-09-20 21:46:27 UTC
Without any code, it's hard to see what is going wrong, and impossible to tell if it's a bug in your code or in Apache POI

Can you write a small self-contained junit test case that shows your problem? And ideally also upgrade to the most recent version of Apache POI too?
Comment 3 Sateesh 2016-09-21 13:25:45 UTC
Thanks. I will try to do that and let you know
Comment 4 Dominik Stadler 2016-10-20 20:44:20 UTC
No update for some time and too less information to actually work on this, therefore I am closing this as REMIND for now, please reopen this bug with more information if this is still an issue for you.