Formatting of Exel Cell changed from Number to Custom ([h]:mm:ss)/Custom (mm:ss) format after data filling

Aspose.Cells Product Family
41

Hi,

The number format for datetime issue has been fixed. We have also optimized the performance caused by the number format function to support some locale-dependent formattings enhancement. If you still find the performance issue, please give us a sample project and we will look into it soon. Attached is the latest jar file.

Thanks,

42

Thanks Salman, We will get back to you incase of any issues.

Regards,

Karuppiah

43

The issues you have found earlier (filed as 19057) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
44

Hi Salman

As said in the subject the API "getMaxDataColumn()" returns different values for an excel saved in 2003 format(xls) and 2007 format(xlsx). PFA the demo sample program(AsposeTest.zip) for your reference.

PFA the excels(SAP.xls and SAP.xlsx) for your reference. The API "getMaxDataColumn()" returns a count of 26 for the excel in 2003 format(xls) but returns a count of 16383 for excel in 2007 format(xlsx) although both the excels have the same data, i.e the same number of rows and columns but saved in different formats.

If I use the API "deleteBlankColumns()" and then get the column count, then the API "getMaxDataColumn()" returns a count of 26 for the excel in 2007 format(xlsx) as well. I am not sure as of why there is such discrepencies.

We won't be able to use the API "deleteBlankColumns()" at all the places where API "getMaxDataColumn()" is used because this API has been used across our application and it will not be feasible for us to do so.

Kindly look into this issue and revert as soon as possible as this is a production issue.

Thanks & Regards

Karuppiah M

45

Hi,

Thanks for providing us details.


We have found the issue of Cells.getMaxDataColumn() and
recorded it as CELLSJAVA-19596 into our issue tracking system. We will provide a fix for it soon.<o:p></o:p>

Thank you.


46

Hi Amjad

I need to update the ETC for this issue to customer.

Please share the ETC for this issue.

regards

Karups

47

Hi,

We will provide you a fix within 2 - 3 days.

Thank you.

48

Hi Karu,

Please use the updated version Aspose.CellsV2.4.0.1.zip attached. The issue regarding getMaxDataColumn() has been fixed.

Thanks,

49

Hi Salman,

We are using Aspose Jar version 2.4.0.1. As said in the subject, with this new Jar the API getStringValue() on a cell returns a positive value when the cell with a negative value is formatted in the excel.

PFA the sample xls file to be used, a demo program to showcase this problem and the screen shot on how a negative value was formatted in the excel.

When the demo program is run with the new Jar, getStringValue() returns a positive number 12.00. When the same is run with the old Aspose.Cells.jar version 2.1.0.6, a proper negative value -12.00 is returned.

Kindly look into this issue and revert as soon as possible as this is a production issue. Please let know the ETC for this issue as well so that I can communicate the same to our customer.

Thanks & Regards,

Karuppiah M

50

Hi,

Well, I am afraid it is not a bug. the Cell.getStringValue() should give the same result as Excel shows for a cell having negative value. For the formatted value, it gives and should give 12 for the negative value. We also think if in some older versions the getStringValue() might give -12, then it should be a bug for those older versions.

The bottom line is. If you want to get the inner value of the cell, you should use getValue() method instead of getStringValue() method.

Thank you.

51

Hi Amjad

Thankyou. We wil revert in case of any questions/issues.

Regards

Karuppiah M

52

The issues you have found earlier (filed as 19596) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
53

Hi Amjad,


This is in reference with the number format change (Number to Custom ([h]:mm:ss)/Custom (mm:ss)) issue. This issue has started to crop up in Production Environment again.
The latest jar you provided us was (version 2.4.0.1). Find below the details for your reference:

Reference Internal Issue tracker ID: CELLSJAVA-16616

Let us know the reason of why this issue has come up again inspite of your assurances that this was fixed and tested thoroughly.


We are expecting a response from you ASAP as we would need to inform the root cause of this re-curring issue to our Customer ASAP.

Unfortunately, we will not be able to provide any demo programs for you to replicate this issue.You can find the demo template which I have already provided you with for the above given Issue tracker ID.

Regards

Karuppiah

54

Hi,

We could not reproduce the issue that was previously logged as: CELLSJAVA-16616. Please try our attached latest version/fix v2.5.1.1. If you still find any issue, kindly do provide more details about your issue, template files and the APIs you have called/used to generate the file(s) (having issue) to help us to figure it out. You may also start a new thread as this thread is getting lengthy.

Thank you.

55

Amjad,

The issue which we have raised is consistenly replicable at the production environment over a period of time. Whenever we asked for a root cause/fix for a issue, you provided us with a new jar version everytime.

Now again you have given another updated version, how can we be sure that this version has the fix for that issue.

Whenever we face this issue, you give us a new version. We end up assuring our customer that this issues is fixed, but eventually it comes up again. The client wants a permanent fix for this issue.

Analyze this issue properly and provide us the root cause. We will take the analysis you will provide us to the customer and let them know that this issue is fixed once and for all.

As stated in the above mail, we have provided you with the Tempate and data Filling excels.

Regards

Karuppaih

56

Amjad,

Any updates on this. As said in the above thread, the solution needs to be informed to the client ASAP. Kindly make note.

Regards

Karuppiah

57

Hi Karuppiah,

Well, for your issue, it is hard for us to figure the issue out because there is no exact environment and test cases to reproduce the issue. At our end, we have tested several situations but have no luck to find the cause of the issue and why you are getting this issue. Anyways, we need more time and do further checks for this issue. Also, our Chinese developers have come back to work now (from their vacations).

Once we have any update about it, we will update you.

Thanks for being patient and sorry for any inconvenience caused!

58
<!–[if gte mso 10]> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";}

<![endif]–>Hi,

Would you please give us more information about your issue? Did you copy data from other workbooks? Please give us the code snippet you used to fill data, or at least please give us the APIs of cells in sequence that you invoked for creating the Excel file(s).
We will check it soon.

Thank you.