Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Get Paper Size of Excel Worksheet & Improved Custom Load Filtering Mechanism using .NET

Sheraz KhanSheraz Khan Member Posts: 12

We are pleased to announce the new release of Aspose.Cells for .NET 17.1.0. The new release includes some valuable features and other enhancements with critical bug fixes. The LoadFilter class allows customizing the loading process as per the properties of the Worksheet. In order to customize the loading process, one has to override the LoadFilter.StartSheet method. Please note, there are just a few properties that can be used for a given worksheet object in this scenario because most of the data and properties have not been loaded yet. The available Worksheet properties are: Name, Index & VisibilityType. Users may change the LoadDataFilterOptions property in their own implementation of LoadFilter class to control the behavior of loading template files. Sometimes, application requirement could be to retrieve the worksheet’s paper size in the unit of Inches, which can now be achieved using the PageSetup.PaperWidth and PageSetup.PaperHeight properties. The PageSetup.PaperWidth and PageSetup.PaperHeight properties are of type double representing the paper width & height in the unit of inches while considering the page orientation. Aspose.Cells APIs store 17 significant digits of double values unlike Excel application which stores only 15 significant digits. Users can override this default behavior of Aspose.Cells APIs while using the newly exposed CellsHelper.SignificantDigits property. The code snippet enforces the Aspose.Cells APIs to use 15 significant digits while storing double values to the spreadsheet files of type XLSX. It has added the CheckCustomNumberFormat property to the WorkbookSettings class. The CheckCustomNumberFormat is useful in checking if the Style.Custom property has been set properly or not. In case the Style.Custom property has been set improperly, that is; the value does not correspond to valid pattern then the Aspose.Cells for .NET APIs will throw CellsException with appropriate message. It has enhanced its core for more stability as well as fixed a few critical bugs. Moreover, there are numerous minor enhancements in order to improve the overall usage of the API. Furthermore, this release has fixed several other issues. For example, issues around reading/writing MS Excel Excel file formats, rendering wordart and smartart shapes, rendering charts and other shapes, manipulating ListObject/Table, formatting and manipulating Pivot Tables, conditional formatting, rendering to HTML file format, rendering images from Excel worksheets, rendering images files from charts and exporting Excel workbooks to PDF format have been resolved. The formula calculation engine is improved too in the new release. This release includes several enhanced features and bug fixes as listed below

• MS Excel 2016 XLSX file containing Waterfall chart cannot be opened via Aspose.Cells APIs
• Bind Worksheet to a Customized Collection object (Aspose.Cells.GridWeb)
• Bind Worksheet to a DataSet object at Run Time (Aspose.Cells.GridWeb)
• Output Excel file is not good when converting an HTML file to Excel file format
• Issue with Date format in German locale when rendering an Excel file to PDF
• Representation of double numbers in Aspose.Cells
• PivotTable.RefreshData takes a lot of time
• Performance of GETPIVOTDATA
• Formulas with GETPIVOTDATA are not being recalculated in the output file
• Some CSS rules ignored when importing HTML
• Images in table has incorrect position
• Content color has been changed
• Content style has been changed
• Contents have been displaced
• Issue with overriding default styling of TH elements
• Column position has been changed while refreshing the Pivot Table
• Merged cells in XLSX are not displayed as merged in HTML
• Horizontal and vertical lines are missing in Pivot Table after converting spreadsheet to PDF
• LoadOptions.LoadFilter is not working expectedly
• YIELD function result inaccurate when CalculateFormula() method is called
• Calculating formula returns different results than MS Excel
• Image rendered incorrectly when a cell has Egyptian pound symbol
• WordArt objects become mere dots in the output PDF
• Area chart is slanted at the end in PDF output unlike MS Excel file
• Unnecessary lines appear in the chart image
• Culture settings are not applying on output chart's image
• Graph is not rendered correctly when spreadsheet is converted to PDF
• Image generated by Aspose.Cells gets distorted when inserted into Docx
• Worksheet contents change after opening and resaving as illustrated in the second screenshot
• Worksheet contents change after opening and resaving as illustrated in the first screenshot
• Dotted cell borders are not retained while converting XLSX to ODS
• Excel files get corrupted after loading and saving via Aspose.Cells APIs

Other most recent bug fixes are also included in this release

Sign In or Register to comment.